chore(mobile): declare 1.2.0, matching what is installed - #2
Merged
Conversation
pubspec still said 1.0.0+1 because CI passes --build-name from the computed tag and never reads it back. With no tags in this repo yet, the first release has to be minted by hand from this value, and publishing 1.0.0 would land below the version already on people's phones.
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.
The first release here has to be minted via
workflow_dispatch, which builds whateverpubspec.yamldeclares - and it still said1.0.0+1, because CI normally passes--build-namefrom the computed tag and never writes it back.Publishing 1.0.0 would put the release below the v1.2.0 already installed on phones, so Obtainium would never offer it and the auto-bump would start from the wrong baseline.
Same version as what is installed: nobody re-downloads, the tag exists for the next bump to count from, and the next
feat:cuts v1.3.0.