Skip to content

chore(deps-dev): bump the npm-dependencies group with 4 updates - #84

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/npm-dependencies-9c1ede6ca5
Closed

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/npm-dependencies-9c1ede6ca5

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 2, 2026 •

Copy link
Copy Markdown
Contributor

Bumps the npm-dependencies group with 4 updates: semantic-release, @semantic-release/exec, @semantic-release/github and conventional-commits-parser.

Updates semantic-release from 23.1.1 to 25.0.5

Release notes

Sourced from semantic-release's releases.

v25.0.5

25.0.5 (2026-06-09)

Bug Fixes

v25.0.4

25.0.4 (2026-06-09)

Bug Fixes

  • code-quality: add missing comma in context object for consistency (493d6cd)

v25.0.3

25.0.3 (2026-01-30)

Bug Fixes

v25.0.2

25.0.2 (2025-11-07)

Bug Fixes

  • deps: update dependency read-package-up to v12 (#3935) (1494cb9)

v25.0.1

25.0.1 (2025-10-19)

Bug Fixes

v25.0.1-beta.3

25.0.1-beta.3 (2025-10-19)

Bug Fixes

  • deps: update to latest npm plugin (a96aced)

... (truncated)

Commits
  • db8ffaa fix(revert): next (#4200)
  • 4e476de docs: update README to include information about the new core engine integration
  • 493d6cd fix(code-quality): add missing comma in context object for consistency
  • d05e160 refactor: replace direct logger and env-ci replacements with a mockCore funct...
  • 4f464a7 test: add tests for core delegation and dry-run policy handling
  • 3f5d1b7 refactor: integrate core; remove unused imports and restructuring the main ...
  • 7d71f2e refactor: remove obsolete release type constants and notes separator
  • 1ae1a19 refactor: remove obsolete test files for logger, git, sensitive data handling...
  • bedddc4 refactor: remove obsolete Git-related utilities and logging functions
  • 7172195 refactor(tests): remove obsolete tests for plugins and verification
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for semantic-release since your current version.


Updates @semantic-release/exec from 6.0.3 to 7.1.0

Release notes

Sourced from @​semantic-release/exec's releases.

v7.1.0

7.1.0 (2025-05-09)

Features

  • error: print more useful error for non-process failure (#449) (a285bc5)

v7.0.3

7.0.3 (2025-02-03)

Bug Fixes

  • deps: update dependency execa to v9 (643e2eb)

v7.0.2

7.0.2 (2025-02-01)

Bug Fixes

  • deps: update dependency @​semantic-release/error to v4 (#353) (471f963)

v7.0.1

7.0.1 (2025-02-01)

Bug Fixes

  • deps: update dependency parse-json to v8 (#394) (080440f)

v7.0.0

7.0.0 (2025-01-31)

Features

BREAKING CHANGES

  • the minimum required version of semantic-release to use @semantic-release/exec is now v24.1.0; the warn logger method/function is now available to use in plugin

  • @semantic-release/exec is now a native ES Module. It has named exports for each plugin hook (verifyConditions, analyzeCommits, verifyRelease, generateNotes, prepare, publish, addChannel, success, fail)

... (truncated)

Commits
  • a285bc5 feat(error): print more useful error for non-process failure (#449)
  • aa1a2bc chore(deps): lock file maintenance (#451)
  • b0dc7ab chore(deps): update dependency ava to v6.3.0 (#450)
  • 93bf408 chore(deps): lock file maintenance (#448)
  • 0e70c6f chore(deps): lock file maintenance (#446)
  • e643dc3 ci(action): update actions/setup-node action to v4.4.0 (#445)
  • a08859e chore(deps): lock file maintenance (#444)
  • da1754e chore(deps): lock file maintenance (#443)
  • 72668cc chore(deps): lock file maintenance (#442)
  • 3c6a8a9 chore(deps): update dependency sinon to v20 (#441)
  • Additional commits viewable in compare view

Updates @semantic-release/github from 9.2.6 to 12.0.9

Release notes

Sourced from @​semantic-release/github's releases.

v12.0.9

12.0.9 (2026-07-01)

Bug Fixes

  • asset-upload: stop setting content-length header manually (241f966), closes #1224
  • local-undici: always use the locally installed undici instead of the node built-in version (40973e3), closes #1224
  • publish: handle content-length header properly for asset uploads (#1260) (28e3741), closes #1224 #1224

v12.0.8

12.0.8 (2026-05-08)

Bug Fixes

  • deps: update dependency http-proxy-agent to v9 (#1203) (edd1652)

v12.0.7

12.0.7 (2026-05-08)

Bug Fixes

  • deps: update dependency https-proxy-agent to v9 (#1204) (1f17362)

v12.0.6

12.0.6 (2026-02-12)

Bug Fixes

  • latest: add make_latest property to the GH release PATCH request during publish (#1169) (f516337)

v12.0.5

12.0.5 (2026-02-07)

Bug Fixes

  • latest: add make_latest property to the GH release POST request during publish (#1157) (38051ba)

v12.0.4

12.0.4 (2026-02-06)

Bug Fixes

  • remove failTitle arg in findSRIssues call (#1164) (f7bdd88)

... (truncated)

Commits
  • 28e3741 fix(publish): handle content-length header properly for asset uploads (#1260)
  • 241f966 fix(asset-upload): stop setting content-length header manually
  • 40973e3 fix(local-undici): always use the locally installed undici instead of the nod...
  • 8879ae4 chore(deps): update dependency prettier to v3.9.1 (#1259)
  • bf720e2 chore(deps): update dependency prettier to v3.9.0 (#1258)
  • b34e0ec chore(deps): update dependency prettier to v3.8.5 (#1257)
  • b445fa0 chore(deps): update dependency ls-engines to v0.10.1 (#1256)
  • 4ca0ef4 chore(deps): lock file maintenance (#1255)
  • bb9fdb3 chore(deps): update dependency undici to v7.28.0 [security] (#1254)
  • 059c6ce ci(action): update actions/checkout action to v7 (#1252)
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​semantic-release/github since your current version.


Updates conventional-commits-parser from 5.0.0 to 7.0.0

Release notes

Sourced from conventional-commits-parser's releases.

conventional-commits-parser: v7.0.0

⚠ BREAKING CHANGES

  • packages now require Node.js 22 or newer.

Features

Bug Fixes

conventional-commits-parser: v6.4.0

Features

  • support RegExp in noteKeywords, issuePrefixes, and referenceActions (#1441) (f84bfc4), closes #1436

conventional-commits-parser: v6.3.0

Features

Bug Fixes

  • deduplicate references when the same issue appears multiple times (#1425) (836ac77)
  • default gitlab revert message does not use a final dot in commit message. (#1422) (7391edf)
  • escape special chars in tokens (#1418) (2536e21)

conventional-commits-parser: v6.2.1

Bug Fixes

  • support ClickUp-style issue IDs ending with letters (#1407) (557450b)

conventional-commits-parser: v6.2.0

Features

  • named capturing groups support for regex patterns (#1372) (a63c3f3)

Bug Fixes

  • respect comment char while truncate to scissors (#1373) (a964ccc)

conventional-commits-parser: v6.1.0

Features

  • conventional-commits-parser: allow @ in scope part of the header (#1283) (d48c660)

Bug Fixes

... (truncated)

Changelog

Sourced from conventional-commits-parser's changelog.

7.0.0 (2026-06-26)

⚠ BREAKING CHANGES

  • packages now require Node.js 22 or newer.

Features

Bug Fixes

6.4.0 (2026-03-29)

Features

  • support RegExp in noteKeywords, issuePrefixes, and referenceActions (#1441) (f84bfc4), closes #1436

6.3.0 (2026-03-01)

Features

Bug Fixes

  • deduplicate references when the same issue appears multiple times (#1425) (836ac77)
  • default gitlab revert message does not use a final dot in commit message. (#1422) (7391edf)
  • escape special chars in tokens (#1418) (2536e21)

6.2.1 (2025-10-20)

Bug Fixes

  • support ClickUp-style issue IDs ending with letters (#1407) (557450b)

6.2.0 (2025-06-09)

Features

  • named capturing groups support for regex patterns (#1372) (a63c3f3)

Bug Fixes

  • respect comment char while truncate to scissors (#1373) (a964ccc)

6.1.0 (2025-01-15)

... (truncated)

Commits
  • ed9862d chore(release): monorepo release (#1474)
  • f9195d5 fix(conventional-commits-parser,template): keep footers out of breaking notes...
  • de5e136 feat!: require node 22
  • ede319a ci: migrate to oxlint (#1467)
  • fd799c8 chore(deps): typescript 6 (#1463)
  • 08f44dc chore(release): monorepo release (#1442)
  • f84bfc4 feat(conventional-commits-parser): support RegExp in noteKeywords, issuePrefi...
  • 44bc44d chore(release): monorepo release (#1423)
  • 441af37 docs: fix libraries io links
  • 7d27d06 feat(conventional-changelog,conventional-changelog-writer,conventional-commit...
  • Additional commits viewable in compare view
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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will 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 version will 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

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>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Jul 2, 2026
@Theauxm

Theauxm commented Jul 2, 2026

Copy link
Copy Markdown
Member

@dependabot rebase

@dependabot @github

dependabot Bot commented on behalf of github Jul 2, 2026

Copy link
Copy Markdown
Contributor Author

Looks like these dependencies are updatable in another way, so this is no longer needed.

@dependabot dependabot Bot closed this Jul 2, 2026
@Theauxm
Theauxm deleted the dependabot/npm_and_yarn/npm-dependencies-9c1ede6ca5 branch July 6, 2026 17:16
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant