Skip to content

Repair wp/5.6 branch Actions: Always read the Node.js version from .nvmrc - #84959

Open
desrosj wants to merge 5 commits into
fix-actions-5.6/pin-runner-imagesfrom
fix-actions-5.6/read-node-version-from-nvmrc
Open

desrosj wants to merge 5 commits into
fix-actions-5.6/pin-runner-imagesfrom
fix-actions-5.6/read-node-version-from-nvmrc

Conversation

@desrosj

@desrosj desrosj commented Oct 16, 2026 •

Copy link
Copy Markdown
Member

Part of #82937.

What?

Replaces the hardcoded node-version: 12.x literal on every actions/setup-node step across wp/5.6's workflows with node-version-file: '.nvmrc', so .nvmrc becomes the one source of truth for the Node.js version this branch tests against — all 9 occurrences across five workflows:

Workflow Jobs updated
bundle-size.yml build
create-block.yml build
end2end-test.yml admin-1, admin-2, admin-3, admin-4
static-checks.yml check
unit-test.yml unit-js, unit-php

Because each step's name also carried the version (Use Node.js 12.x), it is renamed to Setup Node.js in the same commit — leaving the version in the name would reintroduce exactly the duplication this change removes.

The mobile-unit-js job's setup step isn't included: that job is removed earlier in this stack (#84957).

No functional change. .nvmrc reads 12 at this point in the stack, the same version the literals pinned, so every affected job resolves to the same Node.js version as before; only the mechanism changes. Each workflow is a separate commit.

Why?

Without this, every Node.js version change on this branch means editing 9 hardcoded literals and 9 step names across five files, which can silently drift apart from .nvmrc and from each other. With it, a version change is a one-line edit to .nvmrc: the Node.js 12 → 14 upgrade later in this stack (#84960) only changes .nvmrc.

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.

@desrosj desrosj added the [Type] Build Tooling Issues or PRs related to build tooling label Oct 16, 2026
@desrosj desrosj self-assigned this Oct 16, 2026
@coderabbitai

coderabbitai Bot commented Oct 16, 2026 •

Copy link
Copy Markdown

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: a5c4a7a7-4f17-4645-a02b-20850247652d

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

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

@github-actions

Copy link
Copy Markdown

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.

@desrosj desrosj changed the title Repair wp/5.6 branch Actions: Always read Node.js version from .nvmrc file Repair wp/5.6 branch Actions: Always read the Node.js version from .nvmrc Oct 16, 2026

@ramonjd ramonjd left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The failing checks fail the same way on the base PR, and pass at the top of this stack (#84978).

@desrosj
desrosj removed this pull request from stack #84979 October 21, 2026 18:30
@desrosj
desrosj added this pull request to stack #85319 October 21, 2026 18:30

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

[Type] Build Tooling Issues or PRs related to build tooling

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants