Repository navigation
Harden external TestFlight upload claims - #31
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.
What changed
pilot uploadthe immediately following commandAPP_STORE_ELIGIBLEbuildWhy
An upload can succeed remotely while the client is interrupted before it records local provenance. A mutable version/build lookup cannot prove which IPA produced that remote build, and concurrent runners must not both cross the non-idempotent upload boundary.
Impact
A successful run permanently retains both mode-400 records. A pending attempt is an incident: automation will not delete, recover, associate, or notify it, and the release owner must preserve it and cut a new build number.
Validation
make checkgate passedmake tooling-check