Skip to content

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 16, 2025

This PR contains the following updates:

Package Change Age Confidence
@semantic-release/github ^11.0.3 -> ^12.0.0 age confidence
semantic-release ^24.2.6 -> ^25.0.0 age confidence

Release Notes

semantic-release/github (@​semantic-release/github)

v12.0.0

Compare Source

Features
  • node-versions: drop support for node versions v20, v21, and v23 (6e2ac27)
  • node-versions: raise the minimum node version requirement for the v24 range (4d6924d)
  • remove github search api consumption (#​1037) (d260bfd), closes #​1022
BREAKING CHANGES
  • node-versions: the minimum node version for the v24 range is now v24.10.0
  • @semantic-release/github no longer consumes the GitHub Search API in the plugin
  • node-versions: a minimum of node v22.14 is now required
semantic-release/semantic-release (semantic-release)

v25.0.0

Compare Source

Bug Fixes
  • deps: update dependency hosted-git-info to v9 (9fa04f8)
  • deps: update dependency yargs to v18 (#​3745) (cde9a72)
  • deps: update to the stable version of the github plugin (f12cf81)
  • deps: update to the stable version of the release-notes-generator plugin (d9def72)
  • deps: updated to the stable version of the commit-analyzer plugin (291533b)
  • deps: upgrade to the beta of the github plugin (b56bddf)
  • deps: upgrade to the beta of the npm plugin (1600e35)
  • deps: upgrade to the new major version of the npm plugin (1be8290)
Features
  • node-versions: drop support for node versions v20, v21, and v23 (56d16f4)
  • node-versions: raise the minimum node version for the v24 range (116a188)
BREAKING CHANGES
  • node-versions: the minimum node version for the v24 range is now v24.10.0
  • node-versions: a minimum of node v22.14 is now required

Configuration

📅 Schedule: Branch creation - Between 08:00 AM and 05:59 PM, Monday through Friday ( * 8-17 * * 1-5 ) in timezone Europe/Berlin, Automerge - Between 08:00 AM and 05:59 PM, Monday through Friday ( * 8-17 * * 1-5 ) in timezone Europe/Berlin.

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the renovate label Oct 16, 2025
@renovate renovate bot requested a review from a team as a code owner October 16, 2025 10:51
@renovate renovate bot added the renovate label Oct 16, 2025
Copy link
Contributor Author

renovate bot commented Oct 16, 2025

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/semantic-release
npm error   dev semantic-release@"^25.0.0" from the root project
npm error   peer semantic-release@">=20.1.0" from @semantic-release/[email protected]
npm error   node_modules/@semantic-release/commit-analyzer
npm error     dev @semantic-release/commit-analyzer@"^13.0.1" from the root project
npm error     @semantic-release/commit-analyzer@"^13.0.1" from [email protected]
npm error   6 more (@semantic-release/exec, @semantic-release/git, ...)
npm error
npm error Could not resolve dependency:
npm error peer semantic-release@"^24.0.0" from [email protected]
npm error node_modules/gradle-semantic-release-plugin
npm error   dev gradle-semantic-release-plugin@"^1.10.1" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/semantic-release
npm error   peer semantic-release@"^24.0.0" from [email protected]
npm error   node_modules/gradle-semantic-release-plugin
npm error     dev gradle-semantic-release-plugin@"^1.10.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2025-10-22T00_06_44_392Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-10-22T00_06_44_392Z-debug-0.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants