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 #83387
September 22, 2026 19:40
desrosj
removed this pull request from stack #83387
September 22, 2026 21:48
desrosj
changed the base branch from
fix-actions-7.0/guard-setaccessible-php85
to
wp/7.0
September 22, 2026 21:48
desrosj
force-pushed
the
fix-actions-7.0/disable-cache-for-release-builds
branch
from
September 22, 2026 21:49
c4160c5 to
69a2c34
Compare
desrosj
changed the base branch from
wp/7.0
to
fix-actions-7.0/reference-trunk-workflow-lint
September 22, 2026 21:51
desrosj
added this pull request to stack #83409
September 22, 2026 21:52
desrosj
removed this pull request from stack #83409
September 28, 2026 15:38
desrosj
changed the base branch from
fix-actions-7.0/reference-trunk-workflow-lint
to
wp/7.0
September 28, 2026 15:38
desrosj
force-pushed
the
fix-actions-7.0/disable-cache-for-release-builds
branch
from
September 28, 2026 15:43
69a2c34 to
d0f4f9e
Compare
desrosj
changed the base branch from
wp/7.0
to
fix-actions-7.0/reference-trunk-workflow-lint
September 28, 2026 15:43
desrosj
added this pull request to stack #83630
September 28, 2026 15:43
desrosj
marked this pull request as ready for review
September 28, 2026 16: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. |
desrosj
force-pushed
the
fix-actions-7.0/disable-cache-for-release-builds
branch
from
October 7, 2026 13:42
d0f4f9e to
948921c
Compare
desrosj
removed this pull request from stack #83630
October 7, 2026 18:13
desrosj
changed the base branch from
fix-actions-7.0/reference-trunk-workflow-lint
to
wp/7.0
October 7, 2026 18:13
desrosj
force-pushed
the
fix-actions-7.0/disable-cache-for-release-builds
branch
from
October 7, 2026 18:16
0d22ad1 to
4cc7fd8
Compare
desrosj
changed the base branch from
wp/7.0
to
fix-actions-7.0/reference-trunk-workflow-lint
October 7, 2026 18:17
desrosj
added this pull request to stack #84187
October 7, 2026 18:18
desrosj
removed this pull request from stack #84187
October 8, 2026 21:10
desrosj
changed the base branch from
fix-actions-7.0/reference-trunk-workflow-lint
to
wp/7.0
October 8, 2026 21:10
desrosj
force-pushed
the
fix-actions-7.0/disable-cache-for-release-builds
branch
from
October 8, 2026 21:12
4cc7fd8 to
0496760
Compare
desrosj
changed the base branch from
wp/7.0
to
fix-actions-7.0/reference-trunk-workflow-lint
October 8, 2026 21:13
desrosj
added this pull request to stack #84347
October 8, 2026 21:13
desrosj
removed this pull request from stack #84347
October 9, 2026 23:27
desrosj
changed the base branch from
fix-actions-7.0/reference-trunk-workflow-lint
to
wp/7.0
October 9, 2026 23:27
desrosj
force-pushed
the
fix-actions-7.0/disable-cache-for-release-builds
branch
from
October 9, 2026 23:28
0496760 to
7e9a935
Compare
desrosj
changed the base branch from
wp/7.0
to
fix-actions-7.0/reference-trunk-workflow-lint
October 9, 2026 23:30
desrosj
added this pull request to stack #84468
October 9, 2026 23:30
lucatume
approved these changes
Oct 20, 2026
desrosj
removed this pull request from stack #84468
October 21, 2026 18:35
desrosj
added this pull request to stack #85325
October 21, 2026 18:35
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 #82782.
What?
Sets
package-manager-cache: falseexplicitly on everyactions/setup-nodestep in the workflows that build and publish release artifacts on this branch (4 steps).build-plugin-zip.ymlbuildbuild-plugin-zip.ymlnpm-publishpublish-npm-packages.ymlreleasepublish-npm-packages.ymlreleaseIt also adds the
cacheinput from 9983882 to.github/setup-node/action.yml. The input defaults totrue. When it isfalse, the action skips thenode_modulescache step and its post-install step, and turns off the npm cache. This branch has nosetup-npmaction, so the npm cache is turned off through thecacheoption ofactions/setup-nodeinstead.Why?
Cache poisoning is an attack in which a release workflow picks up build state cached by an earlier, less-trusted workflow run. A job that produces a published plugin ZIP or npm package should install from the lockfile every time.
actions/setup-node'spackage-manager-cacheinput defaults totrue. It currently engages only whenpackage.jsondeclarespackageManager(ordevEngines.packageManager) naming npm — which this branch does not. That means these jobs are uncached by accident, not by intent: adding that field later would silently switch caching back on in the release path with no visible change to any workflow file. Stating it explicitly removes that dependency on unrelated packaging metadata.How?
Ports WordPress/gutenberg#79835, "Disable caching when publishing built assets", adapted for this branch. Upstream routes these jobs through the composite
.github/setup-nodeaction and threads a newcacheinput through to.github/setup-npm; this branch has nosetup-npmcomposite and its release jobs callactions/setup-nodedirectly, so the equivalent input is set on each step instead.The composite
.github/setup-nodeon this branch now has thecacheinput described above, but none of the release workflows use it: they callactions/setup-nodedirectly, so they are covered bypackage-manager-cache: falseinstead. The Storybook check opts out of the composite action's cache in #84179.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.
🤖 Generated with Claude Code