ci(version): unify base fetch with saas repos#51
Conversation
|
Warning Review limit reached
Next review available in: 47 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)
📝 WalkthroughWalkthroughThe "Resolve version (dispatch)" step in version.yml now determines the current version by listing non-draft, non-pre-release release tags, filtering to ChangesVersion Resolution Workflow
Estimated code review effort: 1 (Trivial) | ~5 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 |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/workflows/version.yml:
- Around line 40-43: In the version workflow, the release lookup pipeline in the
latest-tag assignment is exiting early under set -euo pipefail when grep finds
no semver tags, so the fallback message is never reached. Update the pipeline
around the latest variable in version.yml so the command substitution can
tolerate grep returning no matches (for example by neutralizing that failure
before the [[ -n "$latest" ]] check), preserving the existing "No x.y.z releases
found" handling.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: ae376eb7-3199-479e-8895-ecc9fc2c0fc3
📒 Files selected for processing (1)
.github/workflows/version.yml
Uniform version base across all org repos, same block as flamingo-stack/openframe-saas-shared#1366: newest non-prerelease release via
gh release list | sort -Vinstead of thereleases/latestendpoint. No behavior change here (no promote flow, Latest badge == newest release), pure consistency so the dispatch block is byte-identical in all 7 repos.Summary by CodeRabbit