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/github to v9 #283

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 2, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@semantic-release/github 8.0.7 -> 9.2.6 age adoption passing confidence

Release Notes

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

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)

Configuration

📅 Schedule: 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 added the dependencies label Jun 2, 2023
@renovate
Copy link
Contributor Author

renovate bot commented Jun 2, 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 unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/semantic-release
npm ERR!   dev semantic-release@"19.0.5" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer semantic-release@">=20.1.0" from @semantic-release/[email protected]
npm ERR! node_modules/@semantic-release/github
npm ERR!   dev @semantic-release/github@"9.2.6" 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/2023-12-22T22_42_29_790Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-9-semantic-release-monorepo branch 2 times, most recently from b268f5d to 31e2609 Compare June 8, 2023 05:31
@renovate renovate bot force-pushed the renovate/major-9-semantic-release-monorepo branch from 31e2609 to 2a3f382 Compare July 16, 2023 03:26
@renovate renovate bot force-pushed the renovate/major-9-semantic-release-monorepo branch 2 times, most recently from c1719b6 to f94984c Compare September 14, 2023 13:56
@renovate renovate bot force-pushed the renovate/major-9-semantic-release-monorepo branch 4 times, most recently from 4747040 to 772f891 Compare September 28, 2023 00:07
@renovate renovate bot force-pushed the renovate/major-9-semantic-release-monorepo branch 2 times, most recently from 645cbe9 to ea9e054 Compare November 9, 2023 23:11
@renovate renovate bot force-pushed the renovate/major-9-semantic-release-monorepo branch from ea9e054 to 8885932 Compare November 29, 2023 23:38
@renovate renovate bot force-pushed the renovate/major-9-semantic-release-monorepo branch from 8885932 to 037d93e Compare December 7, 2023 19:07
@renovate renovate bot force-pushed the renovate/major-9-semantic-release-monorepo branch from 037d93e to 7ea0000 Compare December 22, 2023 22:42
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.

0 participants