Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency semantic-release to v23 #457

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 16, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
semantic-release 21.0.5 -> 23.1.1 age adoption passing confidence

Release Notes

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

v23.1.1

Compare Source

v23.1.0

Compare Source

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

v23.0.6

Compare Source

Bug Fixes

v23.0.5

Compare Source

v23.0.4

Compare Source

v23.0.3

Compare Source

v23.0.2

Compare Source

Bug Fixes

v23.0.1

Compare Source

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

v23.0.0

Compare Source

Bug Fixes
Features
BREAKING CHANGES

related to https://github.com/semantic-release/semantic-release/discussions/3088

v22.0.12

Compare Source

Bug Fixes
  • Revert "fix(deps): update dependency cosmiconfig to v9" (#​3104) (f6f1bf1)

v22.0.11

Compare Source

Bug Fixes
  • deps: update dependency cosmiconfig to v9 (b38cd2e)

v22.0.10

Compare Source

Bug Fixes
  • revert updating cosmiconfig to v9 (88efead)

v22.0.9

Compare Source

Bug Fixes

v22.0.8

Compare Source

Bug Fixes

v22.0.7

Compare Source

Bug Fixes
Features

v22.0.6

Compare Source

Bug Fixes

v22.0.5

Compare Source

Bug Fixes

v22.0.4

Compare Source

Bug Fixes

v22.0.3

Compare Source

Bug Fixes

v22.0.2

Compare Source

Bug Fixes
  • deps: update dependency marked-terminal to v6 (8a7befe)

v22.0.1

Compare Source

Bug Fixes
  • deps: upgraded release-notes-generator and commit-analyzer plugins to stable versions (041e4f7), closes #​2934

v22.0.0

Compare Source

Bug Fixes
  • deps: updated to the latest beta of the commit analyzer plugin (03a687b)
  • deps: updated to the latest betas of the commit-analyzer and release-notes-generator plugins (de8e4e0)
  • deps: upgraded to the latest version of the npm plugin with npm v10 (a23b718)
Features
  • conventional-changelog-presets: supported new preset format (07a79ea)
  • defined exports for the package (72ab317)
  • node-versions: raised the minimum node v20 requirement to v20.6 (e623cc6)
  • node-versions: raised the minimum required node version to v18.17 and dropped v19 support (b9f294d)
  • node-versions: raised the minimum supported node version w/in the v20 range to v20.6.1 (b93bef4)
BREAKING CHANGES
  • node-versions: the minimum supported version for the v20 range of node has been raised slightly to
    v20.6.1 to avoid a known node bug
  • node-versions: the minimum supported node version in the v20 major range is now v20.6
  • node-versions: node v18.17 is now the minimum supported node version and support for v19 has been dropped
  • exports prevents access to internal files, but they arent intended for public use anyway
  • conventional-changelog-presets: the new preset format is a breaking change when compared to the previous preset format. updating to support the new format means that the old preset format is no longer supported. update your preset to the latest version to maintain compatibility. this is also important if you are using a preset outside of the list of official conventional-changelog presets since your preset will need to be updated to export async functions to match the expected preset signature.

v21.1.2

Compare Source

Bug Fixes

v21.1.1

Compare Source

Bug Fixes
  • types: included the definitions file in the published package (#​2920) (4c95c97)

v21.1.0

Compare Source

Features

v21.0.9

Compare Source

Bug Fixes

v21.0.8

Compare Source

Bug Fixes

v21.0.7

Compare Source

Bug Fixes

v21.0.6

Compare Source

Bug Fixes
  • get correct version if prerelease branch shares version with ... (#​2416) (e4229f9)

Configuration

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

🚦 Automerge: Enabled.

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 has been generated by Mend Renovate. View repository job log here.

@renovate
Copy link
Contributor Author

renovate bot commented Sep 16, 2023

⚠ 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 ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: jest-react@0.14.0
npm ERR! Found: jest@29.6.2
npm ERR! node_modules/jest
npm ERR!   dev jest@"29.6.2" from the root project
npm ERR!   peer jest@"^29.0.0" from ts-jest@29.1.0
npm ERR!   node_modules/ts-jest
npm ERR!     dev ts-jest@"29.1.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer jest@"^23.0.1 || ^24.0.0 || ^25.1.0" from jest-react@0.14.0
npm ERR! node_modules/jest-react
npm ERR!   dev jest-react@"0.14.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: jest@25.5.4
npm ERR! node_modules/jest
npm ERR!   peer jest@"^23.0.1 || ^24.0.0 || ^25.1.0" from jest-react@0.14.0
npm ERR!   node_modules/jest-react
npm ERR!     dev jest-react@"0.14.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-04-09T22_59_03_678Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-04-09T22_59_03_678Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 13237f1 to 01e7093 Compare September 24, 2023 18:43
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from ed6e708 to 726a1a6 Compare November 3, 2023 21:33
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 726a1a6 to 71d9dd4 Compare November 17, 2023 04:09
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from 837dd3f to e543749 Compare December 12, 2023 00:20
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from e543749 to f99f4e2 Compare December 12, 2023 04:45
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from f99f4e2 to 955740c Compare January 12, 2024 23:24
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v22 chore(deps): update dependency semantic-release to v23 Jan 12, 2024
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from b1fac0a to 362f258 Compare February 7, 2024 16:07
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 3 times, most recently from b746c48 to f51dee8 Compare March 18, 2024 16:50
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from f51dee8 to c42acf8 Compare March 24, 2024 19:01
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch 2 times, most recently from deeeccb to 9215ffe Compare April 9, 2024 22:59
@renovate renovate bot force-pushed the renovate/major-semantic-release-monorepo branch from 9215ffe to 545204f Compare May 10, 2024 20:18
Copy link
Contributor Author

renovate bot commented May 10, 2024

⚠️ 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 error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: jest-react@0.14.0
npm error Found: jest@29.6.2
npm error node_modules/jest
npm error   dev jest@"29.6.2" from the root project
npm error   peer jest@"^29.0.0" from ts-jest@29.1.0
npm error   node_modules/ts-jest
npm error     dev ts-jest@"29.1.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer jest@"^23.0.1 || ^24.0.0 || ^25.1.0" from jest-react@0.14.0
npm error node_modules/jest-react
npm error   dev jest-react@"0.14.0" from the root project
npm error
npm error Conflicting peer dependency: jest@25.5.4
npm error node_modules/jest
npm error   peer jest@"^23.0.1 || ^24.0.0 || ^25.1.0" from jest-react@0.14.0
npm error   node_modules/jest-react
npm error     dev jest-react@"0.14.0" 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-05-10T20_18_40_928Z-eresolve-report.txt

npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-05-10T20_18_40_928Z-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.

None yet

0 participants