Repository navigation
ci: let each Node.js and WordPress version finish when another fails - #2652
Merged
Merged
Conversation
josephfusco
marked this pull request as ready for review
October 16, 2026 21:00
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.
Related #2643, #2651
On #2643 the Node 24 e2e job showed as failed only because GitHub cancelled it when Node 20 failed, which made a Node 20-only npm crash look like it affected two versions;
verify-published-plugin.ymlalready setsfail-fast: false, andcheck-packages.ymlis left alone because it runs a single Node version.Use of AI Tools
AI assistance: Yes
Tool(s): Claude Code
Model(s): Claude Opus 5.5
Used for: Assisting with tracing the cancelled Node 24 job and finding which workflows run version matrices.