ci: Put semantic-release deps under Renovate

[MaxymVlasov]

Description of your changes

These deps were not updated for a long time, and now there are a bunch of major versions on top of it.
I'll update them later via Renovate, this PR is to enable tracking of new versions.

Found during #1021.

How can we test changes

Merge and check the Renovate dashboard - these deps should be added to it too

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: 8402c9f6-2aa2-433d-b543-20d2e2e8f700

📥 Commits

Reviewing files that changed from the base of the PR and between 32e301b and 991fdec.

📒 Files selected for processing (1)

• .github/workflows/release.yml

Included review availability: Your plan provides up to 8 included reviews per hour; 7 remain after this review.

---

📝 Summary

Summary by CodeRabbit

• Chores
  • Centralized release-tool version declarations in the release workflow.
  • Added automated dependency-update metadata for improved version maintenance.
  • Preserved existing release workflow behavior.

Walkthrough

The release workflow moves semantic-release package versions into file-level environment variables with Renovate annotations. The Release step uses those variables while retaining the existing resolved versions.

Changes

Release version management

Layer / File(s)	Summary
Centralize release versions .github/workflows/release.yml	The workflow defines Renovate-annotated environment variables for the three semantic-release package versions. The Release step references these variables instead of inline version values.

Priority: ⬇️ Low

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

Change: Other

Merge Risk: ⚪ Minimal · up to 991fd

The workflow preserves the pinned release versions and uses supported Renovate lookup configuration, with no identified merge-blocking risk.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the main change: placing semantic-release dependencies under Renovate management in CI.
Description check	✅ Passed	The description explains why the dependency tracking changes are needed and how to verify that Renovate detects them.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch update_semantic_release_versions

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[Copilot]

🟢 Approval recommended

No unresolved review comments; the changes only enable dependency tracking.

Pull request overview

Enables Renovate tracking for semantic-release dependencies without changing their current versions.

Changes:

• Adds Renovate annotations and workflow-level version variables.
• Uses the variables in the release action configuration.

File summaries

File	Summary
.github/workflows/release.yml	Centralizes semantic-release dependency versions for Renovate updates.

Review details

• Files reviewed: 1/1 changed files
• Comments generated: 0
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.