Skip to content

chore(deps): update semantic-release monorepo - #650

Open
renovate[bot] wants to merge 1 commit into
devfrom
renovate/semantic-release-monorepo
Open

renovate[bot] wants to merge 1 commit into
devfrom
renovate/semantic-release-monorepo

Conversation

@renovate

@renovate renovate Bot commented Oct 10, 2025

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@semantic-release/npm 11.0.211.0.3 age confidence
semantic-release 23.0.223.1.1 age confidence

Release Notes

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

v11.0.3

Compare Source

Bug Fixes

even though our existing range allowed anyone to update as soon as the new npm version was available, this will encourage being on a version that does not report the ip vulnerability a bit more forcefully

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

v23.1.1

Compare Source

Bug Fixes

v23.1.0

Compare Source

Features

v23.0.8

Compare Source

Bug Fixes
  • deps: rename read-pkg-up -> read-package-up (4980cba)
  • deps: rename read-pkg-up -> read-package-up (#​3249) (95a8b9e)

v23.0.7

Compare Source

Bug Fixes
  • deps: update dependency find-versions to v6 (6a2b6bb)

v23.0.6

Compare Source

Bug Fixes

v23.0.5

Compare Source

Bug Fixes

v23.0.4

Compare Source

Bug Fixes

v23.0.3

Compare Source

Bug Fixes

Configuration

📅 Schedule: (UTC)

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

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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 force-pushed the renovate/semantic-release-monorepo branch from a3fba28 to 2da07e9 Compare November 10, 2025 19:33
@renovate
renovate Bot force-pushed the renovate/semantic-release-monorepo branch from 2da07e9 to cec7ac6 Compare December 3, 2025 18:30
@renovate
renovate Bot force-pushed the renovate/semantic-release-monorepo branch from cec7ac6 to c9a32f7 Compare February 12, 2026 16:30
@renovate
renovate Bot force-pushed the renovate/semantic-release-monorepo branch from c9a32f7 to 7b12bbc Compare March 5, 2026 14:09
@renovate
renovate Bot force-pushed the renovate/semantic-release-monorepo branch from 7b12bbc to 09f8b2e Compare March 13, 2026 18:47
@renovate
renovate Bot force-pushed the renovate/semantic-release-monorepo branch from 09f8b2e to f3235bd Compare April 1, 2026 18:47
@renovate
renovate Bot force-pushed the renovate/semantic-release-monorepo branch from f3235bd to 738fd15 Compare May 12, 2026 11:32
@renovate
renovate Bot force-pushed the renovate/semantic-release-monorepo branch from 738fd15 to 04b52ae Compare June 11, 2026 18:43
@renovate
renovate Bot force-pushed the renovate/semantic-release-monorepo branch from 04b52ae to ff68807 Compare July 12, 2026 12:05
@renovate
renovate Bot force-pushed the renovate/semantic-release-monorepo branch from ff68807 to 2b9d4cf Compare July 30, 2026 20:16
@renovate
renovate Bot force-pushed the renovate/semantic-release-monorepo branch from 2b9d4cf to 784cc59 Compare September 2, 2026 20:48
@renovate

renovate Bot commented Sep 15, 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-10.9.9.tgz"
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-09-16T13_05_43_867Z-debug-0.log

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.

0 participants