-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
tools: ensure daily wpt nightly node version can be installed #46891
Merged
nodejs-github-bot
merged 1 commit into
nodejs:main
from
panva:fix-wpt-nightly-missing-build
Mar 1, 2023
Merged
tools: ensure daily wpt nightly node version can be installed #46891
nodejs-github-bot
merged 1 commit into
nodejs:main
from
panva:fix-wpt-nightly-missing-build
Mar 1, 2023
Conversation
This file contains 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
Review requested:
|
nodejs-github-bot
added
the
meta
Issues and PRs related to the general management of the project.
label
Mar 1, 2023
Fast-track has been requested by @panva. Please 👍 to approve. |
richardlau
approved these changes
Mar 1, 2023
panva
added
the
author ready
PRs that have at least one approval, no pending requests for changes, and a CI started.
label
Mar 1, 2023
cjihrig
approved these changes
Mar 1, 2023
panva
added
commit-queue
Add this label to land a pull request using GitHub Actions.
and removed
commit-queue
Add this label to land a pull request using GitHub Actions.
labels
Mar 1, 2023
anonrig
approved these changes
Mar 1, 2023
anonrig
added
the
commit-queue
Add this label to land a pull request using GitHub Actions.
label
Mar 1, 2023
nodejs-github-bot
removed
the
commit-queue
Add this label to land a pull request using GitHub Actions.
label
Mar 1, 2023
Landed in 3860087 |
targos
pushed a commit
that referenced
this pull request
Mar 13, 2023
PR-URL: #46891 Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]>
targos
pushed a commit
that referenced
this pull request
Mar 14, 2023
PR-URL: #46891 Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]>
danielleadams
added
the
dont-land-on-v18.x
PRs that should not land on the v18.x-staging branch and should not be released in v18.x.
label
Apr 3, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
author ready
PRs that have at least one approval, no pending requests for changes, and a CI started.
dont-land-on-v18.x
PRs that should not land on the v18.x-staging branch and should not be released in v18.x.
fast-track
PRs that do not need to wait for 48 hours to land.
meta
Issues and PRs related to the general management of the project.
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.
This PR updates the nightly version query to ensure that a build for platform linux and architecture x64 exists by adding a query to jq, it is now looking for the first listed nightly with
"linux-x64"
in files.This will avoid the issue that occurred during the latest run possibly caused by a nightly build failing. See
v20.0.0-nightly202302287a37829ccb
in https://nodejs.org/download/nightly/index.json