chore(deps): update dependency @semantic-release/github to v10 (main) - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@semantic-release/github	9.2.6 -> 10.0.3

---

Release Notes

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

v10.0.3

Compare Source

v10.0.2

Compare Source

Bug Fixes

• deps: update octokit monorepo (major) (#​792) (97e368d)

v10.0.1

Compare Source

Bug Fixes

• deps: update dependency issue-parser to v7 (#​798) (8140ba8)

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

---

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

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign andrienkoaleksandr for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[openshift-merge-robot]

PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.