Release v3.0.4: fix release automation#28
Conversation
Two CI fixes so version-bump pushes release end-to-end without manual tag re-pushing:
- auto-tag.yml: a tag pushed with GITHUB_TOKEN does not fire the Release
workflow's `on: push: tags` trigger (GitHub blocks recursive event
triggering). Explicitly dispatch release.yml via `gh workflow run`
(workflow_dispatch is exempt from that restriction; needs actions: write).
- release.yml: the "Resolve tag" step used ${GITHUB_REF_NAME:-inputs.tag},
which on workflow_dispatch resolves to the branch (master), failing the
version-match check. Prefer the explicit input: inputs.tag || ref_name.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Warning Review limit reached
More reviews will be available in 51 minutes. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (3)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
1 participant
Fixes the two release-pipeline bugs found while shipping v3.0.3, and bumps to v3.0.4 so the corrected flow is exercised end-to-end on merge.
Fixes
auto-tag.yml— a tag pushed withGITHUB_TOKENdoes not firerelease.yml'son: push: tagstrigger (GitHub blocks recursive event triggering), so releases never auto-started. Now explicitly dispatchesrelease.ymlviagh workflow run(workflow_dispatch is exempt from that restriction). Addsactions: writepermission.release.yml—Resolve tagused${GITHUB_REF_NAME:-inputs.tag}, which onworkflow_dispatchresolves to the branch (master) and fails the version-match check. Now usesinputs.tag || ref_name.Expected post-merge behavior
Merge →
auto-tagcreatesv3.0.4and dispatchesrelease.yml→ release builds the.vsix+ GitHub Release automatically (no manual tag re-push). Marketplace publish remains the manualvscestep by design.No
src/changes — extension bundle is functionally identical to 3.0.3.🤖 Generated with Claude Code