This repository was archived by the owner on Jul 31, 2026. It is now read-only.
ci: bump node20 actions to node24 runtime - #351
Merged
Conversation
pnpm/action-setup v4 and amannn/action-semantic-pull-request v5 ship the deprecated node20 runtime, triggering CI deprecation warnings. Bump both to v6 (node24). v5+ of action-setup reads the pnpm version from package.json's packageManager field, already present. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
2 issues found across 6 files
Confidence score: 4/5
- This PR is likely safe to merge, with moderate but non-blocking CI/CD security hardening gaps rather than an immediate functional regression risk.
- The most significant issue is in
.github/workflows/publish.yml, wherepnpm/action-setup@v6is a floating tag; if that tag is retargeted upstream, pipeline behavior could change unexpectedly and weaken supply-chain integrity. - A similar mutable-tag exposure exists in
.github/workflows/typecheck.yml; pinning third-party actions to immutable commit SHAs would reduce tampering risk and improve build reproducibility. - Pay close attention to
.github/workflows/publish.ymland.github/workflows/typecheck.yml- both rely on mutable action tags instead of commit SHAs.
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name=".github/workflows/publish.yml">
<violation number="1" location=".github/workflows/publish.yml:22">
P2: The workflow uses a floating GitHub Action tag (`pnpm/action-setup@v6`) instead of pinning to a commit SHA, which weakens CI/CD supply-chain integrity.</violation>
</file>
Reply with feedback, questions, or to request a fix.
Fix all with cubic | Re-trigger cubic
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
What
Bump two GitHub Actions still running the deprecated node20 runtime to node24:
pnpm/action-setup@v4@v6amannn/action-semantic-pull-request@v5@v6Why
CI emits node20 runtime deprecation warnings. These two were the only actions still on node20 —
actions/checkout@v6,actions/setup-node@v6, andcycjimmy/semantic-release-action(v6.0.0) already run node24.Notes
pnpm/action-setupv5+ resolves the pnpm version frompackageManagerinpackage.json(pnpm@11.4.0, already present) — noversioninput needed.🤖 Generated with Claude Code
Summary by cubic
Upgrade remaining CI actions from the deprecated node20 runtime to node24 to remove deprecation warnings and keep workflows consistent.
pnpm/action-setup:@v4➝@v6(usespackageManagerinpackage.json; noversioninput needed)amannn/action-semantic-pull-request:@v5➝@v6Written for commit dc77521. Summary will update on new commits.