Repository navigation
chore(release): build release candidates as the version they precede - #160
Merged
Merged
Conversation
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.
A tag such as
v0.0.25-rc1now builds version 0.0.25 with the next Xcode Cloud build number, so one version can have several TestFlight builds and the version number grows only when a release is cut.AGENTS.mdsays to tag a candidate soon after any merge that changes what a person sees or does, and to cut the release when a candidate has been tried or a set of work is complete.Checks
The build script was run against
v0.0.25,-rc1,-rc12(all build 0.0.25) and-beta, a fourth number,v0.0.0-rc1andvfoo(all refused).Review depth: checks only. It changes a tag-build script and instructions, and no app code.