Skip to content

ci(version): unify base fetch with saas repos#51

Merged
yaroslavmokflmg merged 2 commits into
masterfrom
hotfix/version-base-unify
Jul 9, 2026
Merged

ci(version): unify base fetch with saas repos#51
yaroslavmokflmg merged 2 commits into
masterfrom
hotfix/version-base-unify

Conversation

@yaroslavmokflmg

@yaroslavmokflmg yaroslavmokflmg commented Jul 9, 2026

Copy link
Copy Markdown

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 -V instead of the releases/latest endpoint. 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

  • Chores
    • Improved version detection to use the highest valid release version when determining the current app version.
    • Added a safeguard that stops the process if no matching release version is available.

@coderabbitai

coderabbitai Bot commented Jul 9, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@yaroslavmokflmg, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 47 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 4f9b0c0e-d4a1-4979-a76a-7bd4bbfb528c

📥 Commits

Reviewing files that changed from the base of the PR and between 103c288 and ac32e4e.

📒 Files selected for processing (1)
  • .github/workflows/version.yml
📝 Walkthrough

Walkthrough

The "Resolve version (dispatch)" step in version.yml now determines the current version by listing non-draft, non-pre-release release tags, filtering to x.y.z pattern, and selecting the highest semantic version via sort, instead of querying the releases/latest endpoint.

Changes

Version Resolution Workflow

Layer / File(s) Summary
Resolve version step update
.github/workflows/version.yml
Replaces releases/latest lookup with gh release list, tag filtering to x.y.z pattern, semantic version sorting, and error handling when no matching tags exist.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

Suggested reviewers: ivan-flamingo

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately reflects the workflow change to unify version base-fetch behavior with the SaaS repositories.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch hotfix/version-base-unify

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

📥 Commits

Reviewing files that changed from the base of the PR and between 46eb1b5 and 103c288.

📒 Files selected for processing (1)
  • .github/workflows/version.yml

Comment thread .github/workflows/version.yml
@yaroslavmokflmg yaroslavmokflmg merged commit 3140028 into master Jul 9, 2026
5 checks passed
@yaroslavmokflmg yaroslavmokflmg deleted the hotfix/version-base-unify branch July 9, 2026 17:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants