Repository navigation
Conversation
desrosj
changed the base branch from
fix-actions-6.5/remove-rn-workflows
to
fix-actions-6.5/update-actions-to-latest
August 26, 2026 14:11
desrosj
force-pushed
the
fix-actions-6.5/single-node-version-testing
branch
3 times, most recently
from
August 27, 2026 15:02
e63becc to
539d58c
Compare
desrosj
removed this pull request from stack #87
September 10, 2026 19:37
desrosj
force-pushed
the
fix-actions-6.5/single-node-version-testing
branch
from
September 10, 2026 19:39
539d58c to
281beec
Compare
desrosj
added this pull request to stack #190
September 10, 2026 19:40
desrosj
force-pushed
the
fix-actions-6.5/single-node-version-testing
branch
2 times, most recently
from
September 11, 2026 00:26
77425da to
7291c2f
Compare
desrosj
force-pushed
the
fix-actions-6.5/single-node-version-testing
branch
3 times, most recently
from
September 11, 2026 02:30
8806c94 to
22255a0
Compare
desrosj
force-pushed
the
fix-actions-6.5/single-node-version-testing
branch
from
September 14, 2026 01:57
22255a0 to
a2a625f
Compare
desrosj
marked this pull request as ready for review
September 15, 2026 19:01
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
This removes the `check-latest: true` input from every `actions/setup-node` call within: - the composite `.github/setup-node/action.yml` action - `build-plugin-zip.yml` - `bundle-size.yml` - `static-checks.yml` - `pull-request-automation.yml` `check-latest: true` makes `actions/setup-node` query the Node.js release index for a newer matching version on every run before falling back to its local tool cache. That's only useful when the Node.js version in use is still actively receiving new releases. This branch pins Node.js `20` via `.nvmrc` which has reached end-of-life and will never be updated. This results in extra unnecessasry HTTP requests per run rather than a meaningful freshness check.
This removes the `node` matrix dimension from the `checks` job in `create-block.yml`. Unlike newer branches, this workflow has no `event`-based excludes tied to the `node` dimension, so only the matrix entry and job name need updating. The `node-version` input for the `./.github/setup-node` step has been eliminated and the action will fall back to the value in the `.nvmrc` file.
This removes the `node` matrix dimension from the `unit-js` job in `unit-test.yml`. Since `node` was the job's only matrix dimension (this branch predates the shard-based splitting used on newer branches, and date tests run as a step within this same job rather than a separate `unit-js-date` job), the entire `strategy` block is removed. The `node-version` input for the `./.github/setup-node` step has been eliminated and the action will fall back to the value in the `.nvmrc` file.
…-packages.yml`. This removes the `check-latest: true` input from both `actions/setup-node` calls in `publish-npm-packages.yml`, completing the change already made elsewhere in this layer. `check-latest: true` makes `actions/setup-node` query the Node.js release index for a newer matching version on every run before falling back to its local tool cache. That's only useful when the Node.js version in use is still actively receiving new releases. This branch pins Node.js `20` via `.nvmrc` which has reached end-of-life and will never be updated. This results in extra unnecessary HTTP requests per run rather than a meaningful freshness check. This file didn't exist when the original removal commit was made in this layer (it had been removed by a prior layer and has since been restored), so it never received this change until now.
desrosj
force-pushed
the
fix-actions-6.5/single-node-version-testing
branch
from
September 15, 2026 19:22
a2a625f to
bfa885a
Compare
desrosj
removed this pull request from stack #190
September 15, 2026 21:18
desrosj
added this pull request to stack #376
September 15, 2026 21:22
Owner
Author
|
Migrated to the real |
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
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.
What?
This trims the testing matrix for workflow files that test multiple versions of Node.js.
Additinoally, the
check-latest: trueinput is removed from everyactions/setup-nodecall.Why?
These workflows tested both the current and next Node.js version when the branc was created to catch forward-compatibility issues early. Since this branch is only eligible for security updates, it will never run on anything but the Node.js version pinned in
.nvmrc. Testing additional versions wastes time running Actions unnecessarily.The
check-latest: trueinput makesactions/setup-nodere-check for a newer matching release on every single run, useful only while the pinned version is still receiving releases. Node.js 20.x has reached end-of-life.Use of AI Tools
This PR was created by Claude Code under my supervision. All code should be treated as AI-produced and not yet reviewed by a human until this PR is marked Ready for Review.