Repository navigation
ci: wait for the published version to be installable before creating the release - #94
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.
npm processes new versions for a few minutes after the upload is accepted (publish-time scanning); qrcodets 1.0.1 took several minutes to appear after the GitHub release was already created.
pnpm publish --publish-wait-timeout 600000(pnpm 12.7+) waits up to 10 minutes until the exact version is installable, sogh release createonly runs once npm serves it. If the wait times out, the upload stays accepted and a rerun skips publishing (version already on the registry) and just creates the release.