ci(release): guard helm chart tag against non-semver mutable tag#50
Conversation
|
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: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughModifies CI workflow logic for release versioning: version.yml now resolves the latest release tag via GitHub's releases/latest API endpoint with x.y.z regex validation, replacing prior multi-release filtering/sorting logic; release.yml maps a 'latest' resolved version to '9.9.9' for the Helm chart tag instead of using 'latest' directly. ChangesRelease version tagging
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
On push, version resolves to a mutable tag (latest/dev) which is not valid OCI semver for the helm chart releaser. Same guard as fleetmdm Ylianst#71: use 9.9.9 placeholder when version is the mutable tag, otherwise the real version. build_helm only stays green today because it's skipped when the chart is unchanged; a push that changes the chart would otherwise fail the helm release.
Summary by CodeRabbit