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 semantic release dependencies to v10 (major) #298

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

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Mar 17, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@semantic-release/git 9.0.0 -> 10.0.1 age adoption passing confidence
@semantic-release/github 7.0.7 -> 10.0.6 age adoption passing confidence

Release Notes

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

v10.0.1

Compare Source

Bug Fixes

v10.0.0

Compare Source

Features
  • node-version: raised the minimum required version to v14.17 (7ab65f8)
BREAKING CHANGES
  • node-version: the minimum required version of node is now v14.17

v9.0.1

Compare Source

Bug Fixes
semantic-release/github (@​semantic-release/github)

v10.0.6

Compare Source

v10.0.5

Compare Source

Bug Fixes

v10.0.4

Compare Source

Bug Fixes
  • introduce dedicated option for GitHub API endpoint (#​829) (908ff83)

v10.0.3

Compare Source

v10.0.2

Compare Source

Bug Fixes

v10.0.1

Compare Source

Bug Fixes

v10.0.0

Compare Source

Features
  • node-versions: dropped support for node v18 and v19 (#​797) (aea314f)
BREAKING CHANGES
  • node-versions: node v18 and v19 are no longer supported

v9.2.6

Compare Source

Bug Fixes

v9.2.5

Compare Source

Bug Fixes

v9.2.4

Compare Source

Bug Fixes

v9.2.3

Compare Source

Bug Fixes

v9.2.2

Compare Source

Bug Fixes

v9.2.1

Compare Source

v9.2.0

Compare Source

Features

v9.1.0

Compare Source

Features
  • releaseNameTemplate and releaseBodyTemplate options for customizing release body and name (#​704) (9e2678c)

v9.0.7

Compare Source

Bug Fixes

v9.0.6

Compare Source

Bug Fixes

v9.0.5

Compare Source

Bug Fixes

v9.0.4

Compare Source

Bug Fixes

v9.0.3

Compare Source

Bug Fixes

v9.0.2

Compare Source

Bug Fixes

v9.0.1

Compare Source

Bug Fixes

v9.0.0

Compare Source

BREAKING CHANGES
  • @semantic-release/github is now a native ES Module
  • Node 14 and 16 are no longer supported

v8.1.0

Compare Source

Features

v8.0.9

Compare Source

Bug Fixes

v8.0.8

Compare Source

Bug Fixes
  • Use Octokit for request retries and throttling to prevent rate limit errors (#​487) (3dc59ec)

v8.0.7

Compare Source

Bug Fixes
  • deps: update dependency fs-extra to v11 (8bba5f0)

v8.0.6

Compare Source

Bug Fixes

v8.0.5

Compare Source

Bug Fixes

v8.0.4

Compare Source

Bug Fixes
  • revert "fix(deps): update dependency url-join to v5" (6e4dfca)

v8.0.3

Compare Source

Bug Fixes
  • deps: update dependency url-join to v5 (7725391)

v8.0.2

Compare Source

Bug Fixes

v8.0.1

Compare Source

Bug Fixes

v8.0.0

Compare Source

BREAKING CHANGES
  • node-version: the minimum required version of node is now v14.17

v7.2.3

Compare Source

Bug Fixes

v7.2.2

Compare Source

Bug Fixes
  • deps: update dependency fs-extra to v10 (1a28625)

v7.2.1

Compare Source

Bug Fixes
  • allow proxy to be false and fallback an empty string (#​356) (bea917f)

v7.2.0

Compare Source

Features

v7.1.2

Compare Source

Bug Fixes

v7.1.1

Compare Source

Bug Fixes

v7.1.0

Compare Source

Features

Configuration

📅 Schedule: Branch creation - "before 4am" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates 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 renovate bot assigned C0ZEN Mar 17, 2024
@renovate renovate bot requested a review from C0ZEN March 17, 2024 02:12
Copy link
Author

renovate bot commented Mar 17, 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 ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: @sonia-corporation/conventional-changelog@1.3.0
npm ERR! Found: semantic-release@17.1.1
npm ERR! node_modules/semantic-release
npm ERR!   dev semantic-release@"17.1.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer semantic-release@">=18.0.0" from @semantic-release/git@10.0.1
npm ERR! node_modules/@semantic-release/git
npm ERR!   dev @semantic-release/git@"10.0.1" 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! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

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

@renovate renovate bot force-pushed the dependencies/major/major-10-semantic-release-dependencies branch from 544c625 to 12220be Compare April 7, 2024 01:37
Copy link
Contributor

github-actions bot commented May 8, 2024

Stale pull request message

@renovate renovate bot force-pushed the dependencies/major/major-10-semantic-release-dependencies branch from 12220be to 8bbc32d Compare May 16, 2024 03:58
Copy link
Author

renovate bot commented May 16, 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 ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: @sonia-corporation/conventional-changelog@1.3.0
npm ERR! Found: semantic-release@17.1.1
npm ERR! node_modules/semantic-release
npm ERR!   dev semantic-release@"17.1.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer semantic-release@">=18.0.0" from @semantic-release/git@10.0.1
npm ERR! node_modules/@semantic-release/git
npm ERR!   dev @semantic-release/git@"10.0.1" 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! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-06-05T02_07_48_502Z-debug.log

@renovate renovate bot force-pushed the dependencies/major/major-10-semantic-release-dependencies branch from 8bbc32d to 018237d Compare May 23, 2024 00:17
@renovate renovate bot force-pushed the dependencies/major/major-10-semantic-release-dependencies branch from 018237d to 728a706 Compare June 5, 2024 02:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant