ci: roll dev-latest tag to dev-HEAD on each publish#94
Conversation
The rolling dev-latest prerelease froze its tag at the commit where this workflow first published: ncipollo/release-action honors `commit:` only when it creates a tag, not on allowUpdates updates. So the tag, the release "target" commit, and `git checkout dev-latest` source all stuck days behind dev while only the body and .7z asset advanced — the release looked dead even though nightly builds ran fine. Force-move the ref to github.sha before the ncipollo publish so the rolling release tracks dev-HEAD. Scoped to release-dev only; the shared publish-release action keeps semver release tags immutable. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Warning Review limit reached
More reviews will be available in 57 minutes and 45 seconds. 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: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ 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 |
There was a problem hiding this comment.
Pull request overview
Updates the release-dev GitHub Actions workflow so the rolling dev-latest tag is actively moved to the exact commit that was built, ensuring the prerelease page/tag/source checkout consistently track dev HEAD rather than the tag’s original creation commit.
Changes:
- Adds a pre-publish step that force-updates (or creates) the
dev-latesttag ref togithub.shavia the GitHub API. - Clarifies inline workflow comments to document why the explicit tag-roll step is necessary with
ncipollo/release-action+allowUpdates.
Problem
The dev nightly is running and succeeding daily — but the
dev-latestrolling prerelease looks frozen. Three references that should be one commit had drifted:devHEADdc88209cac323d9(#79)dev-latesttag →1e8fda46(#58)The tag was pinned to the commit where this workflow first published, ~6 days stale. So the release's target commit and
git checkout dev-latestsource were stale, and the page read as "nightlies stopped" even though the attached.7zwas current.Root cause
publish-releaseusesncipollo/release-actionwithallowUpdates: trueand passescommit:. ncipollo honorscommitonly when creating a tag — on update it never moves an existing ref. The tag pinned to its creation commit forever.Fix
Add a step in
release-dev.yaml'sprereleasejob that force-rolls thedev-latestref togithub.shabefore the ncipollo publish (creating it on first run). The job already hascontents: write.Scoped to
release-devonly — the sharedpublish-releaseaction and its immutable semver release tags are untouched.Verification
YAML lints clean (pre-commit). Effect is observable on the next publish:
dev-latesttag will equal dev-HEAD, matching the body/asset. No mod/runtime code touched (ci:→ no release).