Skip to content

chore(deps): update dependency @semantic-release/github to v12#12

Open
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/semantic-release-github-12.x
Open

chore(deps): update dependency @semantic-release/github to v12#12
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/semantic-release-github-12.x

Conversation

@renovate
Copy link

@renovate renovate bot commented Oct 16, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@semantic-release/github ^9.2.1^12.0.0 age adoption passing confidence

Release Notes

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

v12.0.6

Compare Source

Bug Fixes
  • latest: add make_latest property to the GH release PATCH request during publish (#​1169) (f516337)

v12.0.5

Compare Source

Bug Fixes
  • latest: add make_latest property to the GH release POST request during publish (#​1157) (38051ba)

v12.0.4

Compare Source

Bug Fixes

v12.0.3

Compare Source

Bug Fixes
  • extend GraphQL alias prefix to prevent hash collisions (#​1134) (ea6386d)

v12.0.2

Compare Source

Bug Fixes
  • add undici ProxyAgent support for GitHub Enterprise Server behind proxies (#​1104) (15def77)

v12.0.1

Compare Source

Bug Fixes

v12.0.0

Compare Source

Features
  • node-versions: drop support for node versions v20, v21, and v23 (6e2ac27)
  • node-versions: raise the minimum node version requirement for the v24 range (4d6924d)
  • remove github search api consumption (#​1037) (d260bfd), closes #​1022
BREAKING CHANGES
  • node-versions: the minimum node version for the v24 range is now v24.10.0
  • @semantic-release/github no longer consumes the GitHub Search API in the plugin
  • node-versions: a minimum of node v22.14 is now required

v11.0.6

Compare Source

Bug Fixes

v11.0.5

Compare Source

Bug Fixes

v11.0.4

Compare Source

Bug Fixes

v11.0.3

Compare Source

Bug Fixes

v11.0.2

Compare Source

Bug Fixes

v11.0.1

Compare Source

Bug Fixes

v11.0.0

Compare Source

chore
  • update peer dependency for semantic-release (95c7cdd)
Code Refactoring
  • modify commit associatedPRs and relatedIssues label property data type. (718134a)
Features
  • integrate warn in fail script (7a9914a)
  • integrate warn in success script (792720d)
BREAKING CHANGES
  • the commit associatedPR and relatedIssues label prop is now an array of objects with more properties
  • the minimum required version of semantic-release to use
    @​semantic-release/github is now v24.1.0

v10.3.5

Compare Source

Bug Fixes
  • replace searchAPI usage with GraphQL in findSRIssue util (#​907) (7fb46a3)

v10.3.4

Compare Source

Bug Fixes
  • glob-assets: remove unnecessary option when invoking globby() (#​924) (efe9f49)

v10.3.3

Compare Source

Bug Fixes
  • Revert: feat: verify OAuth scopes of classic GitHub PATs (#​915) (990bd73)

v10.3.2

Compare Source

Bug Fixes
  • missing "PullRequest".canBeRebased field on GHES graphql api (#​913) (4393578)

v10.3.1

Compare Source

Bug Fixes
  • max_node_limit_exceeded error when fetching associatedPRs (#​912) (bb806af)

v10.3.0

Compare Source

Features
  • allow conditional skip on success and fail comments (#​874) (e097d1c)

v10.2.0

Compare Source

Features

v10.1.7

Compare Source

Bug Fixes

v10.1.6

Compare Source

Bug Fixes
  • edge-case: fetching associatedPRs on 100+ context.commits in success lifecycle (#​892) (dfe47e9)

v10.1.5

Compare Source

Bug Fixes

v10.1.4

Compare Source

Bug Fixes
  • docs: correct docs branch for fail-comment links (#​893) (b591730)

v10.1.3

Compare Source

Bug Fixes

v10.1.2

Compare Source

Bug Fixes

v10.1.1

Compare Source

Bug Fixes
  • invalid GraphQL query generated when no release commits are found (#​876) (8ee2744)

v10.1.0

Compare Source

Features

v10.0.7

Compare Source

Bug Fixes
  • replace github search api with graphql in success lifecycle method (#​857) (be394cf)

v10.0.6

Compare Source

Bug Fixes
  • corrected homepage link in package.json so the generated links in the errors are valid (#​848) (865762d)

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

Bug Fixes

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

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
Copy link
Author

renovate bot commented Oct 16, 2025

⚠️ 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 stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: undefined@undefined
npm error Found: semantic-release@22.0.12
npm error node_modules/semantic-release
npm error   dev semantic-release@"^22.0.5" from the root project
npm error
npm error Could not resolve dependency:
npm error peer semantic-release@">=24.1.0" from @semantic-release/github@12.0.6
npm error node_modules/@semantic-release/github
npm error   dev @semantic-release/github@"^12.0.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 /runner/cache/others/npm/_logs/2026-03-14T14_17_33_295Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-03-14T14_17_33_295Z-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