Repository navigation
fix(release): wait for npm to serve platform packages before publishing t3 #18251
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
only21mil
wants to merge
13
commits into
pingdotgg:main
from
only21mil:fix/14409-launcher-tarball-readiness
Closed
Changes from 2 commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
e94c843
test(release): cover the npm readiness wait before the launcher publi…
only21mil aabd910
fix(release): wait for npm to serve platform packages before publishi…
only21mil 0dc4df1
fix(release): keep the underlying error on registry and manifest fail…
only21mil bfe4e79
fix(release): give npm 25 minutes to serve platform packages
only21mil 6ac6887
fix(release): check the registry npm publishes the platform packages to
only21mil c80603c
refactor(release): wait for the platform versions the launcher lists
only21mil 63b5e62
test(release): cover stalled npm reads, concurrent checks and upload …
only21mil b4f6d5e
fix(release): pick the publish registry the way npm does
only21mil c809380
docs(release): say what the timeout recovery does and does not publish
only21mil 14d7ed0
fix(release): keep the npm registry value out of its error
only21mil d16891f
fix(release): read the publish registry with npm config get
only21mil 27a9505
fix(release): probe the npm registry without its login
only21mil 8450db3
docs(release): name the skipped jobs and recovery prerequisites
only21mil File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This maps both filesystem and JSON/schema failures to
BuildAssetMissingError, discarding their underlying errors and reporting malformed manifests as missing. Consider mapping each failure where it occurs to an appropriate structured error with the original failure ascause. No diff suggested: this requires separate error handling and error schema changes.Posted via Macroscope — Effect Service Conventions