chore: update GitHub Actions to use latest versions of actions and Node.js 22 - #381
Conversation
WalkthroughThe PR updates pnpm configuration, moves the workspace to pnpm 10, upgrades CI action versions, switches workflows to Node.js 22, and updates artifact upload/download actions across publishing, testing, and deployment workflows. ChangesCI Toolchain Updates
Estimated code review effort: 2 (Simple) | ~10 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 Checkov (3.3.8).github/workflows/auto-publish.ymlTraceback (most recent call last): .github/workflows/deploy-playground-to-cdn.ymlTraceback (most recent call last): .github/workflows/dispatch-publish.ymlTraceback (most recent call last):
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 |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/workflows/auto-publish.yml:
- Around line 20-30: Update all affected GitHub Actions references to the
requested current versions: checkout and setup-node to v7, pnpm/action-setup to
v6, upload-artifact to v7, and download-artifact to v8. Apply these changes in
.github/workflows/auto-publish.yml (20-30),
.github/workflows/deploy-playground-to-cdn.yml (45-57, 124, 135-138),
.github/workflows/dispatch-publish.yml (38-50),
.github/workflows/pr-ci-build.yml (17-25, 56),
.github/workflows/pr-ci-e2e-test.yml (13-21, 39, 53),
.github/workflows/pr-ci-publish-packages.yml (17-25, 44, 67), and
.github/workflows/pr-deploy-preview.yml (23, 41), preserving each workflow’s
existing configuration.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 7aee3166-0e62-4a73-867b-641d15395896
📒 Files selected for processing (9)
.github/workflows/auto-publish.yml.github/workflows/deploy-playground-to-cdn.yml.github/workflows/dispatch-publish.yml.github/workflows/pr-ci-build.yml.github/workflows/pr-ci-e2e-test.yml.github/workflows/pr-ci-publish-packages.yml.github/workflows/pr-deploy-preview.ymlpackage.jsonpnpm-workspace.yaml
… package.json for cache keys
📦 Package Previewpnpm add https://pkg.pr.new/@opentiny/tiny-robot@4ea8c4d pnpm add https://pkg.pr.new/@opentiny/tiny-robot-kit@4ea8c4d pnpm add https://pkg.pr.new/@opentiny/tiny-robot-svgs@4ea8c4d commit: 4ea8c4d |
|
@coderabbitai review |
✅ Action performedReview finished.
|
There was a problem hiding this comment.
🧹 Nitpick comments (2)
.github/workflows/deploy-playground-to-cdn.yml (2)
72-73: 🚀 Performance & Scalability | 🔵 Trivial | ⚡ Quick winKeep
pnpm-lock.yamlin the cache key.Manifest-only hashing leaves the cache key unchanged when dependency resolutions change solely in
pnpm-lock.yaml. Because installation uses--no-frozen-lockfile, this can cause repeated downloads of newly resolved packages instead of saving a fresh store cache.Proposed fix
- key: ${{ runner.os }}-pnpm-store-${{ hashFiles('**/package.json', 'pnpm-workspace.yaml') }} + key: ${{ runner.os }}-pnpm-store-${{ hashFiles('**/package.json', 'pnpm-workspace.yaml', 'pnpm-lock.yaml') }}🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.github/workflows/deploy-playground-to-cdn.yml around lines 72 - 73, Update the cache key in the workflow’s pnpm store caching step to include pnpm-lock.yaml in the hashFiles inputs alongside the existing package manifests and workspace configuration, ensuring lockfile resolution changes invalidate the cache.
45-58: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick winVerify the action versions against the “latest versions” objective.
As of July 23, 2026, the official actions document newer majors: checkout v7, pnpm/action-setup v6, setup-node v6, cache v6, upload-artifact v7, and download-artifact v8. (github.com)
Either upgrade these references after compatibility testing or adjust the PR objective to state that it intentionally adopts Node 24-compatible, but not latest, versions. Based on learnings, action-runtime upgrades should use Node 24-compatible releases and defer unrelated breaking-major upgrades until compatibility is verified.
Also applies to: 68-69, 125-125, 136-139
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.github/workflows/deploy-playground-to-cdn.yml around lines 45 - 58, Update the workflow’s referenced GitHub Actions to the documented latest majors—checkout v7, pnpm/action-setup v6, setup-node v6, cache v6, upload-artifact v7, and download-artifact v8—after verifying compatibility, including the additional occurrences noted in the comment; otherwise revise the PR objective to explicitly state that it intentionally uses Node 24-compatible non-latest versions.Sources: Learnings, MCP tools
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Nitpick comments:
In @.github/workflows/deploy-playground-to-cdn.yml:
- Around line 72-73: Update the cache key in the workflow’s pnpm store caching
step to include pnpm-lock.yaml in the hashFiles inputs alongside the existing
package manifests and workspace configuration, ensuring lockfile resolution
changes invalidate the cache.
- Around line 45-58: Update the workflow’s referenced GitHub Actions to the
documented latest majors—checkout v7, pnpm/action-setup v6, setup-node v6, cache
v6, upload-artifact v7, and download-artifact v8—after verifying compatibility,
including the additional occurrences noted in the comment; otherwise revise the
PR objective to explicitly state that it intentionally uses Node 24-compatible
non-latest versions.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 497633ad-da73-4b75-b003-c0277ef2b7cb
📒 Files selected for processing (6)
.github/workflows/auto-publish.yml.github/workflows/deploy-playground-to-cdn.yml.github/workflows/dispatch-publish.yml.github/workflows/pr-ci-build.yml.github/workflows/pr-ci-e2e-test.yml.github/workflows/pr-ci-publish-packages.yml
🚧 Files skipped from review as they are similar to previous changes (5)
- .github/workflows/pr-ci-build.yml
- .github/workflows/auto-publish.yml
- .github/workflows/pr-ci-publish-packages.yml
- .github/workflows/dispatch-publish.yml
- .github/workflows/pr-ci-e2e-test.yml
🧹 Preview Cleaned UpThe preview deployment has been removed. |

Summary by CodeRabbit