Skip to content

chore(deps): update dependency semantic-release to v24#268

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

chore(deps): update dependency semantic-release to v24#268
tradeshift-renovate[bot] wants to merge 1 commit into
masterfrom
renovate/major-semantic-release-monorepo

Conversation

@tradeshift-renovate

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
semantic-release devDependencies major ^23.0.0 -> ^24.0.0

Release Notes

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

v24.0.0

Compare Source

Bug Fixes
  • deps: upgraded to the beta of the commit-analyzer plugin (dfc3d91)
  • deps: upgraded to the beta of the release-notes-generator plugin (4a4cd92)
BREAKING CHANGES
  • deps: the commit-analyzer plugin now expects to be used with the latest major versions of
    conventional-changelog packages. if you are installing any of these packages in addition to
    semantic-release, be sure to update them as well
  • deps: the release-notes-generator plugin now expects to be used with the latest major
    versions of conventional-changelog packages. if you are installing any of these packages in addition
    to semantic-release, be sure to update them as well

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

v23.0.2

Compare Source

Bug Fixes

v23.0.1

Compare Source

Bug Fixes
  • deps: update dependency marked-terminal to v7 (9faded8)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻️ Rebasing: Never, 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 has been generated by Renovate Bot.

@tradeshift-renovate tradeshift-renovate Bot requested a review from a team as a code owner June 1, 2024 03:32
@tradeshift-renovate tradeshift-renovate Bot added the dependencies Pull requests that update a dependency file label Jun 1, 2024
@tradeshift-renovate tradeshift-renovate Bot requested a review from a team as a code owner June 1, 2024 03:32
@tradeshift-renovate

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 config cert `key` and `cert` are no longer used for most registry operations.
npm warn config Use registry scoped `keyfile` and `certfile` instead.
npm warn config       Example:
npm warn config       //other-registry.tld/:keyfile=/path/to/key.pem
npm warn config       //other-registry.tld/:certfile=/path/to/cert.crt
npm warn config key `key` and `cert` are no longer used for most registry operations.
npm warn config Use registry scoped `keyfile` and `certfile` instead.
npm warn config       Example:
npm warn config       //other-registry.tld/:keyfile=/path/to/key.pem
npm warn config       //other-registry.tld/:certfile=/path/to/cert.crt
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @rollup/plugin-babel@6.0.3
npm error Found: rollup@4.9.6
npm error node_modules/rollup
npm error   dev rollup@"^4.0.0" from the root project
npm error   peerOptional rollup@"^1.20.0||^2.0.0||^3.0.0||^4.0.0" from @rollup/plugin-json@6.1.0
npm error   node_modules/@rollup/plugin-json
npm error     dev @rollup/plugin-json@"^6.0.0" from the root project
npm error   2 more (@rollup/plugin-node-resolve, @rollup/pluginutils)
npm error
npm error Could not resolve dependency:
npm error peerOptional rollup@"^1.20.0||^2.0.0||^3.0.0" from @rollup/plugin-babel@6.0.3
npm error node_modules/@rollup/plugin-babel
npm error   dev @rollup/plugin-babel@"^6.0.3" from the root project
npm error
npm error Conflicting peer dependency: rollup@3.29.4
npm error node_modules/rollup
npm error   peerOptional rollup@"^1.20.0||^2.0.0||^3.0.0" from @rollup/plugin-babel@6.0.3
npm error   node_modules/@rollup/plugin-babel
npm error     dev @rollup/plugin-babel@"^6.0.3" 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 /tmp/renovate/cache/others/npm/_logs/2024-06-01T03_32_44_434Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-06-01T03_32_44_434Z-debug-0.log

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 dev

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant