You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
chore(deps): update dependency semantic-release to v26 - autoclosed - #2609
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 error in a future major version of npm. See `npm help npmrc` for supported config options.
npm error code EALLOWREMOTE
npm error Fetching packages of type "remote" have been disabled
npm error Refusing to fetch "https://registry.npmjs.org/npm/-/npm-12.2.2.tgz"
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-11-17T00_56_06_575Z-debug-0.log
renovateBot
changed the title
chore(deps): update dependency semantic-release to v26
chore(deps): update dependency semantic-release to v26 - autoclosed
Nov 19, 2026
Superseded: semantic-release v26 landed directly on dev (2b19efa) together with a regenerated root lockfile and the rest of the npm updates, after validating the release config with a local --dry-run. CI's release-dry-run check is green on that commit.
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
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.
This PR contains the following updates:
^25.0.3→^26.0.0Release Notes
semantic-release/semantic-release (semantic-release)
v26.0.1Compare Source
Bug Fixes
v26.0.0Compare Source
Bug Fixes
chore
Features
verifyAuthdry-run operation and isolate branch status check (#3447) (3e2a071), closes #3437BREAKING CHANGES
https://semantic-release.org/support/node-version/#run-at-least-one-ci-job-with-a-version-of-node-that-meets-our-version-requirement
breaking changes at https://github.com/npm/cli/releases/tag/v12.0.0
semantic-releasenow checks if your local branch isup-to-date with your remote repo branch after of push permission
verification.
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.