chore(deps-dev): bump the npm-dependencies group with 4 updates - #84
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps the npm-dependencies group with 4 updates: [semantic-release](https://github.com/semantic-release/semantic-release), [@semantic-release/exec](https://github.com/semantic-release/exec), [@semantic-release/github](https://github.com/semantic-release/github) and [conventional-commits-parser](https://github.com/conventional-changelog/conventional-changelog/tree/HEAD/packages/conventional-commits-parser). Updates `semantic-release` from 23.1.1 to 25.0.5 - [Release notes](https://github.com/semantic-release/semantic-release/releases) - [Commits](semantic-release/semantic-release@v23.1.1...v25.0.5) Updates `@semantic-release/exec` from 6.0.3 to 7.1.0 - [Release notes](https://github.com/semantic-release/exec/releases) - [Commits](semantic-release/exec@v6.0.3...v7.1.0) Updates `@semantic-release/github` from 9.2.6 to 12.0.9 - [Release notes](https://github.com/semantic-release/github/releases) - [Commits](semantic-release/github@v9.2.6...v12.0.9) Updates `conventional-commits-parser` from 5.0.0 to 7.0.0 - [Release notes](https://github.com/conventional-changelog/conventional-changelog/releases) - [Changelog](https://github.com/conventional-changelog/conventional-changelog/blob/master/packages/conventional-commits-parser/CHANGELOG.md) - [Commits](https://github.com/conventional-changelog/conventional-changelog/commits/conventional-commits-parser-v7.0.0/packages/conventional-commits-parser) --- updated-dependencies: - dependency-name: semantic-release dependency-version: 25.0.5 dependency-type: direct:development update-type: version-update:semver-major dependency-group: npm-dependencies - dependency-name: "@semantic-release/exec" dependency-version: 7.1.0 dependency-type: direct:development update-type: version-update:semver-major dependency-group: npm-dependencies - dependency-name: "@semantic-release/github" dependency-version: 12.0.9 dependency-type: direct:development update-type: version-update:semver-major dependency-group: npm-dependencies - dependency-name: conventional-commits-parser dependency-version: 7.0.0 dependency-type: direct:development update-type: version-update:semver-major dependency-group: npm-dependencies ... Signed-off-by: dependabot[bot] <support@github.com>
Member
|
@dependabot rebase |
Contributor
Author
|
Looks like these dependencies are updatable in another way, so this is no longer needed. |
Theauxm
added a commit
that referenced
this pull request
Sep 17, 2026
Same change proven on Trax.Mediator, where it healed #84 end to end. The old workflow could never land a commit: it used `git push`, and the org ruleset requires verified signatures, which a runner has no key for. It now writes through the createCommitOnBranch GraphQL mutation, which GitHub signs itself, so the heal lands Verified with no signing key in CI. It also only ever fixed lockfiles. Dependabot rewrites project files on a grouped bump: when the transitive graph resolves one package at different versions across projects, it adds <PackageReference ... VersionOverride="..."> to projects that never referenced it, several pinned to the version being bumped away from. Nothing reverted those, so lockfiles regenerated on top of the injection. The revert is re-derived with git in the committing job rather than trusted from the patch, so the job that runs dependency code still hands over nothing but lockfiles. The regenerating restore now passes -p:NuGetAudit=false. Directory.Build.props promotes NU1901-NU1904 to errors, so an advisory anywhere in the graph aborted the regeneration, which is precisely the state a security bump arrives in. The PR build still audits. It keeps authenticating with GITHUB_TOKEN rather than an App token or a PAT. Either would avoid the "Approve and run" press on the run that follows the write, but both mean a long-lived credential in Dependabot secrets, and an App private key never expires and can mint write tokens for every repo it is installed on. GITHUB_TOKEN stores nothing. On the config side, csharpier and PublicApiGenerator are ignored. Each has to move in one commit with the artefact it invalidates -- the repo-wide format and the PublicApi baselines -- which a bot PR cannot do, so it just leaves the check failing every time. Roslyn moves to its own group so that when its bump does need a human it does not take the rest of the week's updates with it, and the PR limit drops to three.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps the npm-dependencies group with 4 updates: semantic-release, @semantic-release/exec, @semantic-release/github and conventional-commits-parser.
Updates
semantic-releasefrom 23.1.1 to 25.0.5Release notes
Sourced from semantic-release's releases.
... (truncated)
Commits
db8ffaafix(revert): next (#4200)4e476dedocs: update README to include information about the new core engine integration493d6cdfix(code-quality): add missing comma in context object for consistencyd05e160refactor: replace direct logger and env-ci replacements with a mockCore funct...4f464a7test: add tests for core delegation and dry-run policy handling3f5d1b7refactor: integratecore; remove unused imports and restructuring the main ...7d71f2erefactor: remove obsolete release type constants and notes separator1ae1a19refactor: remove obsolete test files for logger, git, sensitive data handling...bedddc4refactor: remove obsolete Git-related utilities and logging functions7172195refactor(tests): remove obsolete tests for plugins and verificationMaintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for semantic-release since your current version.
Updates
@semantic-release/execfrom 6.0.3 to 7.1.0Release notes
Sourced from @semantic-release/exec's releases.
... (truncated)
Commits
a285bc5feat(error): print more useful error for non-process failure (#449)aa1a2bcchore(deps): lock file maintenance (#451)b0dc7abchore(deps): update dependency ava to v6.3.0 (#450)93bf408chore(deps): lock file maintenance (#448)0e70c6fchore(deps): lock file maintenance (#446)e643dc3ci(action): update actions/setup-node action to v4.4.0 (#445)a08859echore(deps): lock file maintenance (#444)da1754echore(deps): lock file maintenance (#443)72668ccchore(deps): lock file maintenance (#442)3c6a8a9chore(deps): update dependency sinon to v20 (#441)Updates
@semantic-release/githubfrom 9.2.6 to 12.0.9Release notes
Sourced from @semantic-release/github's releases.
... (truncated)
Commits
28e3741fix(publish): handle content-length header properly for asset uploads (#1260)241f966fix(asset-upload): stop settingcontent-lengthheader manually40973e3fix(local-undici): always use the locally installed undici instead of the nod...8879ae4chore(deps): update dependency prettier to v3.9.1 (#1259)bf720e2chore(deps): update dependency prettier to v3.9.0 (#1258)b34e0ecchore(deps): update dependency prettier to v3.8.5 (#1257)b445fa0chore(deps): update dependency ls-engines to v0.10.1 (#1256)4ca0ef4chore(deps): lock file maintenance (#1255)bb9fdb3chore(deps): update dependency undici to v7.28.0 [security] (#1254)059c6ceci(action): update actions/checkout action to v7 (#1252)Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for
@semantic-release/githubsince your current version.Updates
conventional-commits-parserfrom 5.0.0 to 7.0.0Release notes
Sourced from conventional-commits-parser's releases.
... (truncated)
Changelog
Sourced from conventional-commits-parser's changelog.
... (truncated)
Commits
ed9862dchore(release): monorepo release (#1474)f9195d5fix(conventional-commits-parser,template): keep footers out of breaking notes...de5e136feat!: require node 22ede319aci: migrate to oxlint (#1467)fd799c8chore(deps): typescript 6 (#1463)08f44dcchore(release): monorepo release (#1442)f84bfc4feat(conventional-commits-parser): support RegExp in noteKeywords, issuePrefi...44bc44dchore(release): monorepo release (#1423)441af37docs: fix libraries io links7d27d06feat(conventional-changelog,conventional-changelog-writer,conventional-commit...Maintainer changes
This version was pushed to npm by dangreen, a new releaser for conventional-commits-parser since your current version.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions