ci: bump the four GitHub Actions that still declare a node20 runtime - #11
Conversation
GitHub reports on every run that actions/checkout@v4, actions/setup-go@v5, actions/setup-node@v4 and pnpm/action-setup@v4 target Node.js 20 and are being forced to run on Node.js 24. Nothing is broken today - the forcing is already happening - but the pinned majors have not declared support for the runtime they are being given. actions/checkout v4 -> v7 actions/setup-go v5 -> v7 actions/setup-node v4 -> v7 pnpm/action-setup v4 -> v6 Checked against each action's own action.yml rather than assumed: all four declare runs.using: node24 at the new major, pnpm/action-setup@v6.1.0 still accepts the version input this workflow passes, and actions/setup-node@v7.0.0 still accepts node-version, cache and cache-dependency-path. The docker/* actions in deploy-beta.yml and deploy-prod.yml carry the same warning and are deliberately left alone. Bumping them cannot be validated by a pull request - only by triggering a real image build - so they belong in a separate change where a failed build does not also take the beta pipeline down. This pull request is its own test: CI runs it using the new action versions.
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
|
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 configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 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 |
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_a05fe45d-534f-4a82-b87a-71e1e7978baa) |
1 participant
GitHub annotates every run with:
Note
Low Risk
CI-only dependency bumps with no application or deployment logic changes; main risk is rare action behavior differences on future runs.
Overview
Updates CI (
.github/workflows/ci.yml) so backend and frontend jobs use newer action majors that run on supported Node runtimes, addressing GitHub’s node20 deprecation notices on workflow runs.Checkout goes from
v4tov7in both jobs. setup-go movesv5→v7on backend tests. On frontend typecheck, pnpm/action-setup isv4→v6and setup-node isv4→v7; Go/Node versions, caches, and test commands are unchanged.Other workflows (e.g. deploy-beta/prod) still pin older checkout versions and were not part of this diff.
Reviewed by Cursor Bugbot for commit ad50c17. Configure here.