chore(deps): consolidate Dependabot updates (Astro 6, GitHub Actions)#105
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughUpdated GitHub Actions workflow action versions, added a Node 22 setup step for docs CI, and bumped documentation dependencies and Node engine requirement; also added an overrides entry pinning Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.github/workflows/rustdoc.yml:
- Around line 92-94: The workflow currently uses actions/deploy-pages@v5 (step
name "Deploy to GitHub Pages", id "deployment") which requires Node 24 and may
break older self-hosted runners/GHES; either revert/pin the action to a Node‑20
compatible release (e.g., actions/deploy-pages@v4) or add an explicit runner
compatibility check and upgrade path (ensure your runners/GHES support node24)
before switching to `@v5`; update the workflow step to use the chosen action
version or add a pre-flight check step that validates the runner Node runtime
compatibility.
In `@docs/package.json`:
- Around line 31-33: Update the package.json "engines.node" entry to require
Node 22.12.0 or higher to match Astro 6 requirements: locate the "engines"
object (the "engines.node" key) and change its version string from ">=18.0.0" to
">=22.12.0" so builds run on a supported runtime.
🪄 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: defaults
Review profile: CHILL
Plan: Pro
Run ID: bb9d3560-6a1d-4f2b-abb1-50cfc59ab75c
⛔ Files ignored due to path filters (1)
docs/package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (3)
.github/workflows/os-build.yml.github/workflows/rustdoc.ymldocs/package.json
| - name: Deploy to GitHub Pages | ||
| id: deployment | ||
| uses: actions/deploy-pages@v4 | ||
| uses: actions/deploy-pages@v5 |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify actions/deploy-pages@v5 exists and check outputs in action.yml
gh api repos/actions/deploy-pages/releases --jq '.[].tag_name' | head -10
# Check if page_url output is documented
gh api repos/actions/deploy-pages/contents/action.yml?ref=v5 --jq '.content' | base64 -d | grep -A5 'outputs:'Repository: aurintex/pai-os
Length of output: 272
🌐 Web query:
actions/deploy-pages v5 release page_url output
💡 Result:
actions/deploy-pages@v5 still exposes the page_url step output (“The URL of the deployed Pages site”).[1]
Use it like this:
- name: Deploy to GitHub Pages
id: deployment
uses: actions/deploy-pages@v5
- name: Show URL
run: echo "${{ steps.deployment.outputs.page_url }}"(You’ll commonly wire it to the environment URL: url: ${{ steps.deployment.outputs.page_url }}.)[2]
v5.0.0 was released on March 25, 2026.[3]
Sources: [1] [2] [3]
🌐 Web query:
GitHub actions deploy-pages action v5 changelog breaking changes
💡 Result:
actions/deploy-pages@v5 (v5.0.0) breaking changes / migration notes
-
Runtime upgrade to Node.js 24 (
node24): v5.0.0 updates the action’s runtime from Node 20 to Node 24 (“Update Node.js version to 24.x”). This is the main breaking change between v4 and v5. [1]- Practically, this can break workflows on older/self-hosted runners or older GitHub Enterprise Server (GHES) setups that don’t support running JavaScript actions on
node24. The v5 tag points at this Node 24 update. [2][3]
- Practically, this can break workflows on older/self-hosted runners or older GitHub Enterprise Server (GHES) setups that don’t support running JavaScript actions on
-
GHES compatibility: The repo’s compatibility table already flags v4 as “incompatible” with GHES at the time of writing; v5’s move to
node24further implies you must verify GHES/runner support before upgrading. [4]
Changelog sources
- v5.0.0 release notes / changelog: Node 24 upgrade item is listed there. [1]
- PR
#404contains the rationale/details: bump from Node 20.x to 24.x andruns.using: node24. [3]
Verify runner compatibility with actions/deploy-pages@v5 Node 24 runtime requirement.
v5.0.0 is available and maintains the page_url output, but it upgrades the Node.js runtime from Node 20 to Node 24. This breaks compatibility with older self-hosted runners and older GitHub Enterprise Server (GHES) instances that don't support node24. Ensure your runner environment is compatible before deploying this upgrade.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In @.github/workflows/rustdoc.yml around lines 92 - 94, The workflow currently
uses actions/deploy-pages@v5 (step name "Deploy to GitHub Pages", id
"deployment") which requires Node 24 and may break older self-hosted
runners/GHES; either revert/pin the action to a Node‑20 compatible release
(e.g., actions/deploy-pages@v4) or add an explicit runner compatibility check
and upgrade path (ensure your runners/GHES support node24) before switching to
`@v5`; update the workflow step to use the chosen action version or add a
pre-flight check step that validates the runner Node runtime compatibility.
Regenerate lockfile so npm ci matches package.json (sass, @parcel/watcher, chokidar, etc.). Fixes EUSAGE lockfile drift on CI. Co-authored-by: RicciP <rplunger@users.noreply.github.com>
|
|
3 participants
Summary
This PR rolls up open Dependabot dependency bumps into one mergeable change set.
Docs (
docs/)overrides: pin clsx@^2.1.1 so the prerender bundle does not resolve the old clsx@1 hoisted by transitive deps (fixesNamed export 'clsx' not foundduringastro build).GitHub Actions
.github/workflows/rustdoc.yml:actions/configure-pages@v6,actions/deploy-pages@v5(per Dependabot)..github/workflows/os-build.yml:actions/upload-artifact@v7.upload-pages-artifactwas left at v4; it still pairs with the Pages deploy flow used here. Bump separately if you want everything on the latest major.Verification
CI=true npm run buildindocs/(includesgen:rustdocskip,gen:proto,astro build,test:docs).Supersedes
Closes or supersedes the individual Dependabot PRs for the same bumps (e.g. #95–#100, #104). Close those after merge to avoid duplicate work.
Note: Another local branch
chore/consolidate-dependabot-depsexists on a second worktree; this PR useschore/dependabot-consolidate-2026-04instead.Summary by CodeRabbit