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 |
|
Size Change: 0 B Total Size: 1.23 MB ℹ️ View Unchanged
|
|
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. |
da35e06 to
5a59d3e
Compare
5a59d3e to
61452b2
Compare
|
Size Change: 0 B Total Size: 1.23 MB ℹ️ View Unchanged
|
wp/6.0 branch Actions: Update third-party GitHub Actions to their latest releaseswp/6.0 branch Actions: Update GitHub Actions to their latest versions
ntsekouras
left a comment
There was a problem hiding this comment.
LGTM, thanks! This fixes the jobs that were failing at the setup-node step ("Cache service responded with 400" from the old cache service) and the e2e jobs auto-failing because of the retired upload-artifact v2, so Static Analysis, Compressed Size, Create Block (ubuntu/windows), and Mobile pass now, and the "Node.js 20 is deprecated" warnings for the old actions are gone.
The remaining failures aren't related to the actions (Browserslist, wp-env's docker-compose, Playwright install, Node 14 on arm64 macOS) and are fixed further up the stack (all pass in #85149).
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)
Part of #82933.
What?
Bumps every third-party GitHub Action used on the
wp/6.0branch to its current release, pinned by full-length commit SHA:actions/checkoutv2.3.4v7.0.1actions/setup-nodev2.2.2v7.0.0actions/upload-artifactv2.2.2v7.0.1preactjs/compressed-size-actionv2.2.02.10.0Why?
Every one of these pins is multiple years old at this point. Old action releases increasingly run into compatibility problems as GitHub evolves its hosted runners and deprecates the Node.js runtime versions older action releases were built against, which risks these workflows breaking outright with no code change on this branch's part. Updating to current releases, still pinned to an exact commit for reproducibility, keeps CI running reliably without giving up the security benefits of SHA pinning.
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.