fix(ci): use version regex for SUPPLY_TRACK instead of semver is_stable#182
Merged
ErikBjare merged 1 commit intoJul 12, 2026
Conversation
nowsprinting/check-version-format-action@v4 treats 0.x.x versions as not stable (semver convention), but aw-android uses 0.x.x for production releases. This caused SUPPLY_TRACK=internal for all releases, so Play Store uploads went to the internal track instead of production. Replace the is_stable check with a direct regex: X.Y.Z → production, any pre-release suffix (b, rc, dev, alpha, beta) → internal.
5 tasks
Greptile SummaryThis PR updates release track selection for Android publishing.
Confidence Score: 5/5This looks safe to merge.
Important Files Changed
Reviews (1): Last reviewed commit: "fix(ci): use version regex for SUPPLY_TR..." | Re-trigger Greptile |
Contributor
Author
|
CI-green and mergeable (Greptile 5/5) — waiting only on a maintainer click. This PR is ready to merge, but the bot has pull-only access to this repo and can't self-merge — surfacing it here so it isn't lost. The monitoring loop will stop re-flagging it now that this note is posted. |
This was referenced Jul 12, 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.
Problem
The
release-fastlanejob usesnowsprinting/check-version-format-action@v4to determine if a tag is stable, then setsSUPPLY_TRACKaccordingly:The issue:
check-version-format-actionfollows the semver convention where0.x.xversions are not considered stable (they're "development" versions). Since all aw-android releases are0.x.x,is_stableis alwaysfalse, and every release goes to the Play Store internal track instead of production.This caused the
v0.14.0release run to fail withSUPPLY_TRACK=internal, sending the AAB to the wrong track.Fix
Replace the
is_stablecheck with a direct regex on the tag version string:X.Y.Z(no suffix) →productionX.Y.ZbN,X.Y.ZrcN,X.Y.ZdevYYYYMMDD, etc. →internalThis matches how the Release workflow documents it:
Context
Found while investigating the failed
v0.14.0release in issue #176. The other blocker (Target SDK 35 too low) is fixed by PR #179. This PR fixes the track routing so that once #179 merges and the release is re-triggered, the AAB lands in the production track.