tools: run daily WPT.fyi report on all supported releases #55619
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
richardlau
approved these changes
Oct 31, 2024
panva
added
the
author ready
anonrig
approved these changes
Nov 2, 2024
panva
added
the
commit-queue
nodejs-github-bot
removed
the
commit-queue
|
Landed in 57d0ea6 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 updates the Daily WPT report job to always test on all releases that are not EOL + latest nightly and it uses the schedule from https://github.com/nodejs/Release/ to collect the versions.
Example output from the processed schedule given $now is
2024-10-31This resolves an issue with the delay coming from https://github.com/actions/node-versions manifest that
actions/setup-nodeuses as well as actually not cutting off reporting on lts/-2 so long as it's still not EOL presented in the recent run - https://github.com/nodejs/node/actions/runs/11604060841 - where 18 is tested but 22 is not yet, but when actions/node-versions#191 is merged 22 will be tested but 18 will not.