refactor: Bump @semantic-release/github from 12.0.6 to 12.0.9

[mtrezza]

Closes #588

Changes

Bumps the @semantic-release/github devDependency from 12.0.6 to 12.0.9 (patch-level bump; used only in the release/CI pipeline).

Breaking Changes

None. This is a patch-level bump of a development-only dependency and does not affect the published package or runtime behavior.

Code Changes

• package.json: pin @semantic-release/github to 12.0.9.
• package-lock.json: refresh the @semantic-release/github subtree (updated agent-base, http-proxy-agent, https-proxy-agent; added transitive proxy-agent-negotiate). lockfileVersion unchanged.

This replacement PR supersedes the Dependabot PR #588.

Summary by CodeRabbit

• Chores
  • Updated the GitHub release tooling to a newer version.
  • Refreshed related networking components for improved compatibility with current Node.js versions.

[parse-github-assistant]

🚀 Thanks for opening this pull request! We appreciate your effort in improving the project. Please let us know once your pull request is ready for review.

Tip

• Keep pull requests small. Large PRs will be rejected. Break complex features into smaller, incremental PRs.
• Use Test Driven Development. Write failing tests before implementing functionality. Ensure tests pass.
• Group code into logical blocks. Add a short comment before each block to explain its purpose.
• We offer conceptual guidance. Coding is up to you. PRs must be merge-ready for human review.
• Our review focuses on concept, not quality. PRs with code issues will be rejected. Use an AI agent.
• Human review time is precious. Avoid review ping-pong. Inspect and test your AI-generated code.

Note

Please respond to review comments from AI agents just like you would to comments from a human reviewer. Let the reviewer resolve their own comments, unless they have reviewed and accepted your commit, or agreed with your explanation for why the feedback was incorrect.

Caution

Pull requests must be written using an AI agent with human supervision. Pull requests written entirely by a human will likely be rejected, because of lower code quality, higher review effort and the higher risk of introducing bugs. Please note that AI review comments on this pull request alone do not satisfy this requirement. Our CI and AI review are safeguards, not development tools. If many issues are flagged, rethink your development approach. Invest more effort in planning and design rather than using review cycles to fix low-quality code.

[coderabbitai]

📝 Walkthrough

Walkthrough

Changes

Semantic Release GitHub Dependency Bump

Layer / File(s)	Summary
Update semantic-release GitHub version package.json, package-lock.json	@semantic-release/github is upgraded from 12.0.6 to 12.0.9 in the manifest and lockfile metadata.
Refresh proxy-agent resolutions package-lock.json	Proxy-agent packages are upgraded to 9.1.0, agent-base to 9.0.0, and proxy-agent-negotiate 1.1.0 is added with Node 20 engine metadata.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Suggested reviewers: semantic-release-bot

---

Caution

Pre-merge checks failed

Please resolve all errors before merging. Addressing warnings is optional.

• Ignore

❌ Failed checks (1 error, 1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❌ Error	The description does not follow the repository template and is missing the required Issue, Approach, and Tasks sections.	Rewrite the PR description to match the template and include the issue, approach, and task checklist sections.
Engage In Review Feedback	❓ Inconclusive	Review-comment engagement isn't verifiable from repo state; I only see the bump commit and no discussion artifacts.	Provide the PR review thread or GitHub metadata showing a feedback comment plus a reply, commit, or reviewer retraction.

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title matches the requested refactor scope and clearly summarizes the dependency bump.
Linked Issues check	✅ Passed	The PR satisfies #588 by bumping @semantic-release/github to 12.0.9 and refreshing the related lockfile subtree.
Out of Scope Changes check	✅ Passed	The changes are limited to the requested dependency bump and its lockfile updates, with no unrelated scope detected.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Security Check	✅ Passed	Only devDependency/lockfile bumps; no source or install-script changes. Advisory scan found no issues, and undici is 7.24.6—above the patched 7.5.0 threshold.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.18%. Comparing base (9856ea6) to head (dfec981).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #596   +/-   ##
=======================================
  Coverage   99.18%   99.18%           
=======================================
  Files          11       11           
  Lines        1841     1841           
=======================================
  Hits         1826     1826           
  Misses         15       15           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.