Skip registry check on tag legs - #266
Merged
Merged
Conversation
Signed-off-by: Jason Odoom <jason@adastracomputing.com>
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 dispatched run at v0.16.0 failed on the documented-fact drift check: a historical tag's dist-tag pin records the registry as it stood at the tag, so a live registry comparison fails every tag leg forever once a later release publishes. Targets now carry a live flag set only for the current branch head and the drift check runs on that leg alone. Corpus, staged and interop verification still run on every leg.