Problem
The three GitHub workflows (run-checks.yml, run-playwright-tests-anvil-catalog.yml, run-playwright-tests-anvil-cmg.yml) hard-code node-version: "22.12.0", which has drifted from the repo's pinned Node version — package.json engines.node and .gitlab/Dockerfile are at 22.13.0, and #4918 adds a tracked .nvmrc at 22.13.0.
Proposal
Once #4918 merges, replace the hard-coded version in all three workflows with:
- uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0
with:
node-version-file: ".nvmrc"This makes .nvmrc the single source of truth for CI and matches the convention already used in clevercanary/hca-atlas-tracker (run-checks.yml there uses node-version-file: ".nvmrc").
A Node version bump then means updating .nvmrc, engines.node, and .gitlab/Dockerfile together — workflows follow automatically.
Also completes the remaining "workflows on 22.13.0" item from #4876.
Problem
The three GitHub workflows (
run-checks.yml,run-playwright-tests-anvil-catalog.yml,run-playwright-tests-anvil-cmg.yml) hard-codenode-version: "22.12.0", which has drifted from the repo's pinned Node version —package.jsonengines.nodeand.gitlab/Dockerfileare at22.13.0, and #4918 adds a tracked.nvmrcat22.13.0.Proposal
Once #4918 merges, replace the hard-coded version in all three workflows with:
This makes
.nvmrcthe single source of truth for CI and matches the convention already used in clevercanary/hca-atlas-tracker (run-checks.ymlthere usesnode-version-file: ".nvmrc").A Node version bump then means updating
.nvmrc,engines.node, and.gitlab/Dockerfiletogether — workflows follow automatically.Also completes the remaining "workflows on 22.13.0" item from #4876.