ci: build releases only on semver tags and run PR checks for release lines - #3454
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (4)
📜 Recent review details⏰ Context from checks skipped due to timeout. (2)
🧰 Additional context used🧠 Learnings (2)📓 Common learnings📚 Learning: 2026-03-11T06:38:40.426ZApplied to files:
🔇 Additional comments (4)
WalkthroughThe GitHub Actions workflows now trigger release builds only for semantic version tags. PowerShell linting and pull request validation also run for branches matching ChangesWorkflow trigger updates
Estimated code review effort: 1 (Trivial) | ~3 minutes Mergeability Score: ⚪ Minimal · up to This PR adjusts release and pull-request workflow triggers without any identified merge-blocking risk; it is merge-ready after normal checks and review. Suggested labels: Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
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 |
Part of the branching-model migration (dev = development branch, master = releases only, release/X.Y.x = patch lines).
What changed
build-release.ymlno longer triggers on branch pushes (master/dev). Release builds now run only on semver tag pushes (X.Y.ZandX.Y.Z-*). This removes the rolling Development/Snapshot draft builds and makes non-semver tags (archive tags, typos) build-inert.validate-pr.ymlandpull-request-build.ymlnow also run for PRs targetingrelease/**branches — previously patch-release PRs would get no CI at all.powershell-lint.ymlpush trigger extended withrelease/**for consistency.Why
Under the new model, alphas are tagged on
dev, stables onmaster(via dev→master release merges), and patches onrelease/X.Y.xlines. The tag-triggered release path indesktop-release-actionis already branch-agnostic, so no action changes are needed — its per-push dev/snapshot code paths simply become unreachable (left in place deliberately to avoid rebuilding the committeddist/bundle).Validated with actionlint (only pre-existing, unrelated warnings reported).
Summary by CodeRabbit