fix: checkout release tag in publish workflows

[Arthurdw]

Summary

Fixes publish workflows checking out the wrong commit, causing "version already exists" errors.

Problem

When release-pilot runs, it:

1. Bumps versions in files
2. Commits and pushes to main
3. Creates a tag

But the downstream publish workflows (vscode-publish.yml, jetbrains-publish.yml) were checking out the original commit SHA that triggered the workflow, not the new version-bumped commit. This caused the VSCode publish to fail with:

arthurdw.rovo-lsp v0.3.1 already exists.

Solution

• Add ref input to both publish workflows
• Pass the release tag from release-pilot output to publish workflows
• Checkout the tagged commit to ensure the correct version is published

Changes

File	Change
weekly_release.yml	Output tag from release job, pass to publish workflows
vscode-publish.yml	Add ref input, checkout specified ref
jetbrains-publish.yml	Add ref input, checkout specified ref

Summary by CodeRabbit

• Chores
  • Enhanced GitHub Actions workflow configuration to improve coordination between release generation and platform-specific publishing processes. Enables more flexible management of release versions and deployment parameters across distribution channels, providing better control and visibility over artifact distribution to the VSCode extension marketplace and JetBrains plugin repository.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

GitHub Actions workflows are enhanced to support parameterized git references. The jetbrains-publish and vscode-publish workflows now accept an optional ref input parameter, while weekly_release exports the release tag and passes it to these workflows during publishing.

Changes

Cohort / File(s)	Summary
Publish Workflows .github/workflows/jetbrains-publish.yml, .github/workflows/vscode-publish.yml	Add optional ref input parameter to workflow_call. Update checkout step to use provided ref or fallback to github.ref, enabling external callers to specify which git reference to check out.
Release Workflow .github/workflows/weekly_release.yml	Add tag output from Release job. Wire the release tag to both publish workflow invocations via ref: ${{ needs.release.outputs.tag }} parameter.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

• chore: integrate release-pilot for CI/CD automation #18: Directly related to this PR's changes; introduced/rewired the publish workflows and their integration into the weekly_release flow that these parameter additions now enhance.

Suggested labels

CI/CD, release:patch

Poem

🐰 Hop-hop, the workflows now take flight,
With ref parameters shining bright,
Release tags pass from job to job,
A pipeline dance—no need to throb!
The bunny's pipelines now align,
Each checkout picks the perfect line. ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title directly reflects the main change: adding ref checkout capability to publish workflows to fix version-bumped release tag handling.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/publish-workflow-checkout-ref

---

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 and usage tips.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.42%. Comparing base (d004538) to head (66d5975).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #19   +/-   ##
=======================================
  Coverage   92.42%   92.42%           
=======================================
  Files          17       17           
  Lines        5462     5462           
=======================================
  Hits         5048     5048           
  Misses        414      414           

☔ View full report in Codecov by Sentry.
📢 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.