fix(ci): sync-upstream prefers stable releases over prereleases#70
Merged
Conversation
Consistency with the frontend fix: select the newest STABLE release (no -alpha/-beta/-rc suffix), falling back to the newest non-alpha prerelease only when no stable exists. The backend currently only has stable tags so behavior is unchanged (still v11.0.3), but this hardens the selection against any future prerelease tags upstream might publish.
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Change
Mirror of the DOScan-Frontend fix (#6). Tag selection now prefers the newest stable release (no
-suffix), falls back to newest non-alpha prerelease only if no stable exists, and never auto-syncs-alpha.Impact on backend
blockscout/blockscout currently publishes only stable
vX.Y.Ztags, so selection is unchanged (still picksv11.0.3). This is a hardening / consistency change so the two repos share identical sync logic and the backend won't accidentally pull a prerelease if upstream ever tags one.Verified locally
OLD and NEW both pick
v11.0.3. YAML validated.