Repository navigation
fix: wait for newly created VS Code release draft - #981
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.
VS Code releases 0.1.1 and 0.1.2 created their draft successfully, then failed when GitHub’s immediately following release listing did not yet include it. Both recovered through a publication-only retry using the original qualified package.
After the one draft-creation call, allow five read attempts with at most eight seconds of backoff. Only an absent draft triggers another read. Authentication, parsing and duplicate-release errors still propagate, and visible releases immediately enter the unchanged tag, channel and asset-integrity checks. Creation and upload operations are never retried by this change.
This changes future release-source behavior only: no version bump, tag move, package rebuild or modification to the published 0.1.2 release.
Validation: three new regression checks failed before implementation; all 63 Python tests now pass, including real Git/archive and subprocess tests. Ruff F and diff checks pass. The new helper also read the actual public 0.1.2 metadata successfully without mutations. Local policy/metadata tests do not claim that delayed GitHub visibility was reproduced or that this new code ran in the immutable 0.1.2 workflow. Independent parent review found no blocking issues.