Repository navigation
feat(release): show builds in status and wait for a build to process - #522
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.
Fixes #494
What changed
launch statusshows the build attached to each app's current version, with its processing state when it is not VALID. It shows "no build" when none is attached (JSONbuildNumberis null). It reads this from the same versions request, so there is no extra call.launch status --buildslists each app's 25 most recent builds: version, build number, processing state, and upload time in UTC. The app id is looked up once per app.launch status --watch --build <n>waits until build n is VALID and exits. It fails on FAILED or INVALID, and says so when the build never appears before the timeout.--jsonprints one result object withok: trueorok: falseand anerror.launch releasefails fast on FAILED or INVALID instead of waiting 30 minutes. A build that never appears still waits the full 30-minute timeout before it exits 1.--buildwith no iOS app exits 1 with a clear message. A--buildthat is not a whole number above 0 exits 2, and so does--buildwithout--watch, or--buildswith--watch.--account <id>picks the Apple account, the same flaglaunch releasehas. With no flag it uses ASC_ACCOUNT, then the active account.src/core/terminal/table.tsso status and build history share it.Checks
pnpm checkpassed on the pre-push hook: lint, typecheck, docs check, test and build.