ci: auto-tag releases + stamp version from tag (CashPilot-Desktop-rrb)#98
Conversation
…ilot-Desktop-rrb) Desktop releases required a human to push a v* tag and lagged (merged work sat unreleased for days), and wails.json productVersion silently drifted because nothing read or synced it. Add auto-tag.yml: on push to main it computes the next semver from conventional commits since the last tag (same logic as the web repo), pushes the tag, then CALLS desktop-release.yml as a reusable workflow to build/publish. The reusable call is deliberate — a tag pushed with GITHUB_TOKEN does not trigger another workflow, so desktop-release.yml's own tag trigger would silently never fire. A human-pushed tag still triggers it directly, unchanged. desktop-release.yml now stamps productVersion (and both package.json versions) from the tag at build time via jq, so every artifact matches its tag — the drift can no longer happen. Verified with actionlint; jq injection and version-compute logic checked locally.
|
Warning Review limit reached
Next review available in: 29 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ 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 |
|
@coderabbitai review |
✅ Action performedReview finished.
|
1 participant
Problem (PR #96 devops review)
Desktop releases required a human to push a
v*tag, so they lagged — PRs #94/#95 sat merged-but-unreleased for 2+ days — andwails.jsonproductVersionsilently drifted (stayed 0.9.0 through the whole v0.10.0 release; nothing read or validated it).Fix
auto-tag.yml(new): on push to main, compute the next semver from conventional-commit markers since the last tag (feat:→minor,type!:/BREAKING CHANGE→major, else patch — identical to the web repo), push the tag, then calldesktop-release.ymlas a reusable workflow to build/publish.desktop-release.yml: gainsworkflow_call(with aversioninput) and a Set release version step that stampswails.json'sproductVersionand bothpackage.jsonversions from the tag viajqbefore building — so every artifact matches its tag and the drift can no longer happen. The tag is now the single source of truth.Verification
actionlintclean on both workflows.wails.json/productVersion, so the build-time stamp can't breakgo test..github/**, so a workflow-only change never cuts a release; the next code merge to main will release the accumulated work.Closes bead CashPilot-Desktop-rrb.