chore(deps) Update dependency @semantic-release/github to v11

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@semantic-release/github	10.0.6 -> 11.0.1

---

Release Notes

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

v11.0.1

Compare Source

Bug Fixes

• success: PRs not recognized as resolved issues (#​960) (7cde776)

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

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

• verify OAuth scopes of classic GitHub PATs (#​897) (be071a2)

v10.1.7

Compare Source

Bug Fixes

• ignore case when checking for repo rename (#​903) (2b1b9b6), closes #​901

v10.1.6

Compare Source

v10.1.5

Compare Source

Bug Fixes

• compare only / when checking for rename (#​886) (24ea2ee)

v10.1.4

Compare Source

Bug Fixes

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

v10.1.3

Compare Source

Bug Fixes

• Revert "fix: failing release due to renamed repository (#​878)" (#​887) (325952e)

v10.1.2

Compare Source

Bug Fixes

• failing release due to renamed repository (#​878) (76fdaa3)

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

• use branch prerelease property for detection (#​863) (45b8da9)

v10.0.7

Compare Source

Bug Fixes

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

---

Configuration

📅 Schedule: Branch creation - "before 10pm on Sunday" in timezone America/Chicago, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ 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 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]

⚠️ 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 unable to resolve dependency tree
npm error
npm error While resolving: pylint-per-file-ignores@1.3.34
npm error Found: semantic-release@24.0.0
npm error node_modules/semantic-release
npm error   dev semantic-release@"24.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer semantic-release@">=24.1.0" from @semantic-release/github@11.0.1
npm error node_modules/@semantic-release/github
npm error   dev @semantic-release/github@"11.0.1" 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-11-15T09_09_13_679Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-11-15T09_09_13_679Z-debug-0.log