Repository navigation
ci: skip native major versions in the auto-update workflow - #686
Merged
Merged
Conversation
A native major needs a hand-written wrapper major (new pins, the Firebase wrapper, minimums). The daily run now skips a latest release whose major differs from the pinned one; a manual run that names the version can still take it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
mrehan27
approved these changes
Oct 27, 2026
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
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.
The daily native SDK auto-update takes
releases/latestwithout looking at the major. Both native SDKs are on 5.0.0 now, so tomorrow's 09:00 UTC run would open a routine-lookingfeat:PR movingmainto native 5.0 while keepingcioiOSFirebaseWrapperSdkVersionat 1.1.0. That wrapper requiresCustomerIOMessagingPushFCM < 5.0.0, so FCM installs wouldn't resolve, and merging it would ship a native major in a 6.x minor. Native 5.0 lands through #684 instead.With this, a scheduled run skips a latest release whose major differs from the pinned one and leaves a warning in the run. A manual run that names the version still takes it, and patch and minor updates work as before. Merging this or #684 before the next scheduled run avoids the stray PR.
Checked the guard against six cases (new major skipped, same-major patch and minor taken, manual major taken, nothing to do on 5.0.0, API unavailable), and
actionlintreports nothing new.🤖 Generated with Claude Code