Repair wp/7.1 branch Actions: Disable the node_modules cache in the Storybook check

[desrosj]

Part of #82781.

What?

Sets cache: false on the ./.github/setup-node step in the Storybook check workflow (.github/workflows/storybook-check.yml), so the job neither restores nor saves the node_modules and npm caches.

Why?

The Storybook check runs ./.github/setup-node, then runs npm install --no-save @storybook/test-runner@..., which adds and changes packages inside node_modules. At the end of the job, the node_modules cache step saves that modified tree. Its cache key only covers the OS, architecture, Node.js version and lockfile hash, so the modified tree is saved as if it were a clean install. Later jobs on the same ref restore it, skip npm ci, and fail.

For example, on #84039 the Storybook check (https://github.com/WordPress/gutenberg/actions/runs/37631035082) saved the cache after npm install --no-save reported "added 101 packages, changed 29 packages". The Unit Tests run (https://github.com/WordPress/gutenberg/actions/runs/37631034438) restored it a few minutes later, and "Build JavaScript assets for PHP unit tests" failed with TS2307: Cannot find module 'http' and other missing Node.js type errors.

How?

Uses the cache input that #83400 adds to .github/setup-node/action.yml on this branch. With cache: false, the Storybook check always runs a fresh npm ci and never writes its modified node_modules back to the shared cache.

Trunk fixed this differently in b7fb03b, which removed the npm install --no-save step. That change depends on a storybook workspace that this branch does not have.

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

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

• Configuration used: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: d922d7f1-bc2a-4f20-a15c-abe943a0a4ef

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

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 props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: desrosj <desrosj@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.