Skip to content

chore(deps): update dependency semantic-release to v26 - autoclosed - #2609

Closed
renovate[bot] wants to merge 1 commit into
devfrom
renovate/semantic-release-26.x
Closed

renovate[bot] wants to merge 1 commit into
devfrom
renovate/semantic-release-26.x

Conversation

@renovate

@renovate renovate Bot commented Nov 16, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
semantic-release ^25.0.3 → ^26.0.0 age adoption passing confidence

Release Notes

semantic-release/semantic-release (semantic-release)

v26.0.1

Compare Source

Bug Fixes

v26.0.0

Compare Source

Bug Fixes
chore
Features
BREAKING CHANGES

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 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.


  • 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 commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor Author

⚠️ 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 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

@coderabbitai

coderabbitai Bot commented Nov 16, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: f801c842-28ca-472e-a8e8-8510395bd711

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@renovate renovate Bot changed the title chore(deps): update dependency semantic-release to v26 chore(deps): update dependency semantic-release to v26 - autoclosed Nov 19, 2026
@renovate renovate Bot closed this Nov 19, 2026
@renovate
renovate Bot deleted the renovate/semantic-release-26.x branch November 19, 2026 04:16
@Belphemur

Copy link
Copy Markdown
Owner

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.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant