Wait for npm metadata and tarball propagation after publishing - #514
Merged
Conversation
ThreatCrush Security Scan0 finding(s) in the 1 file(s) this pull request changes. Nothing in the files this pull request changes. 94 pre-existing finding(s) elsewhere in the repository — **HIGH/CRITICAL**: 8 | **MEDIUM**: 75 | **LOW**: 11Not introduced by this pull request. The full set is in the Security tab.
…and 74 more. Full results in the Security tab. Snippets are redacted; ThreatCrush never prints matched credential material. |
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.
Releases0.98.3 and0.98.4 published successfully but failed verification because npm propagation exceeded the25-second retry window. Wait up to ten minutes with bounded requests, and verify both version metadata and the downloadable tarball, including reruns where the version already exists.
Validation: parsed the workflow and exercised delayed metadata, delayed tarball, unavailable tarball, wrong version, and already-published scenarios; all five passed. The actual check also passed against public moshcode0.98.4. No package version or application behavior changes.