Repository navigation
Handle delayed NuGet publication with tested bounded retries - #6
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
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.
Adopts Dockyard build-source revision 16a244c6ab8ac286b0a4a5bfd41b5645393680ef: bounded 720-second public-download verification, transient network/rate-limit/server retry handling, immediate immutable-payload mismatch rejection, and 14 verifier tests. Documents recovery using the original validated publication artifacts.
No component runtime or package-version change and no replacement of published packages or tags. The reusable validation workflow stays pinned to its existing tested revision. Merge after Dockyard PR #4 and all native/Blazor checks pass.