Repository navigation
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
desrosj
added this pull request to stack #83694
September 28, 2026 19:40
|
Size Change: 0 B Total Size: 1.63 MB ℹ️ View Unchanged
|
desrosj
marked this pull request as ready for review
September 28, 2026 19:49
|
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. |
desrosj
removed this pull request from stack #83694
September 28, 2026 23:46
desrosj
added this pull request to stack #83741
September 28, 2026 23:46
desrosj
removed this pull request from stack #83741
October 7, 2026 18:11
desrosj
changed the base branch from
fix-actions-6.4/disable-cache-for-release-builds
to
wp/6.4
October 7, 2026 18:12
desrosj
force-pushed
the
fix-actions-6.4/update-actions-to-latest
branch
from
October 7, 2026 18:14
b779822 to
b7db9b3
Compare
desrosj
changed the base branch from
wp/6.4
to
fix-actions-6.4/disable-cache-for-release-builds
October 7, 2026 18:20
desrosj
added this pull request to stack #84191
October 7, 2026 18:20
desrosj
removed this pull request from stack #84191
October 8, 2026 21:38
desrosj
changed the base branch from
fix-actions-6.4/disable-cache-for-release-builds
to
wp/6.4
October 8, 2026 21:38
desrosj
force-pushed
the
fix-actions-6.4/update-actions-to-latest
branch
from
October 8, 2026 21:40
b7db9b3 to
89110ab
Compare
desrosj
changed the base branch from
wp/6.4
to
fix-actions-6.4/disable-cache-for-release-builds
October 8, 2026 21:41
desrosj
added this pull request to stack #84353
October 8, 2026 21:42
desrosj
removed this pull request from stack #84353
October 9, 2026 23:54
desrosj
changed the base branch from
fix-actions-6.4/disable-cache-for-release-builds
to
wp/6.4
October 9, 2026 23:54
desrosj
force-pushed
the
fix-actions-6.4/update-actions-to-latest
branch
from
October 9, 2026 23:56
89110ab to
ed099cb
Compare
desrosj
changed the base branch from
wp/6.4
to
fix-actions-6.4/disable-cache-for-release-builds
October 9, 2026 23:58
desrosj
added this pull request to stack #84480
October 9, 2026 23:58
desrosj
changed the title
wp/6.4 branch Actions: Update third-party actions to their latest releaseswp/6.4 branch Actions: Update GitHub Actions to their latest versions
ntsekouras
approved these changes
Oct 21, 2026
ntsekouras
left a comment
ntsekouras
left a comment
Contributor
There was a problem hiding this comment.
LGTM, thanks! This fixes the jobs that were auto-failing because of the retired actions/cache v3 and upload-artifact/download-artifact v3, so Create Block, Mobile, PHPCS and the flaky tests report pass now, with no Node.js 20 warnings left. Playwright and Puppeteer now actually run, and their failures are fixed further up the stack (all pass in #85134).
Moving to upload-artifact v7 brings the artifact name conflicts for the e2e shards, which I think should be a follow-up row on top of the stack: #84853 (comment).
desrosj
removed this pull request from stack #84480
October 21, 2026 19:42
desrosj
added this pull request to stack #85340
October 21, 2026 19:43
This branch has not been deployed
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.
Part of #82929.
What?
Bumps every third-party GitHub Action used on
wp/6.4to its current latest release, pinned to a full-length commit SHA with a version comment:actions/checkoutv4.0.0v7.0.1actions/setup-nodev3.8.1(workflows) /v3.6.0(.github/setup-node/action.yml)v7.0.0actions/upload-artifactv3.1.3v7.0.1actions/cachev3.3.2(workflows) /v3.3.1(.github/setup-node/action.yml)v6.1.0ramsey/composer-installv2.2.04.0.0shivammathur/setup-phpv2.25.52.37.2preactjs/compressed-size-actionv2.5.02.10.0actions/download-artifact@v3(unpinned tag)v8.0.1actions/setup-nodeandactions/cacheeach had their own separately stale pin inside.github/setup-node/action.yml, the composite action most workflows call into to install Node.js and cache dependencies, in addition to the pins used directly in workflow files that don't go through it. Noactions/upload-artifact/mergesub-action reference exists on this branch.actions/download-artifactwas referenced by an unpinned major-version tag (@v3) in a workflow instead of a commit SHA; that reference is now pinned to a full-length SHA like the rest.Why?
These pins were several major releases behind current, missing security fixes, bug fixes, and compatibility updates (including, for
actions/checkoutandactions/upload-artifact, changes required for continued compatibility with GitHub's runner infrastructure going forward). Some references also relied on an unpinned tag rather than a commit SHA, which is a supply-chain risk since a tag can be moved to point at different code after the fact.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.