ci(docs): bump the SHA-pinned Pages actions to their Node 24 majors

[EtienneLescot]

Problem

#97 moved every tag-pinned action to its Node 24 major. docs.yml pins by SHA instead, so it was left out of that sweep and still logs:

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24 ...

Fix

Bump all four, keeping the SHA pinning this file deliberately uses:

Action	Before	After
actions/checkout	v4.1.1	v7.0.1
actions/setup-node	v4.0.3	v7.0.0
actions/upload-pages-artifact	v3.0.1	v5.0.0
actions/deploy-pages	v4.0.5	v5.0.0

upload-pages-artifact is a composite action, so its own using: is composite; what matters for the warning is the actions/upload-artifact@v7.0.0 it calls internally, which is node24. The other three were verified as node24 by reading action.yml at each pinned SHA.

The one real behavior change

upload-pages-artifact v4 stopped bundling dotfiles. Docusaurus writes a .nojekyll into website/build, so this bump would have silently dropped it.

The artifact-based Pages deploy never runs Jekyll, so losing it would most likely be harmless — but that is not something worth confirming on the live site. include-hidden-files: true (added in v5) restores exactly what v3 uploaded. .git and .github stay excluded either way.

Validation

Changing this file matches the workflow's own paths filter, so the build and upload steps run on this PR.

The deploy job only runs on push to main, so it stays unvalidated until merge. That is the residual risk, and it is small: v4.0.5 → v5.0.0 is a pure runtime bump with no input or output changes.

Not covered

ilammy/msvc-dev-cmd@v1 in build-whisper-stt.yml is the last remaining node20 reference in the repo. Upstream is abandoned (last push April 2024, two open "update to Node 24" PRs unmerged), so there is nothing to bump to — tracked separately.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@EtienneLescot, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 17 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 6e53c156-8f37-4a96-99f7-bc2890ca69f3

📥 Commits

Reviewing files that changed from the base of the PR and between 05cc666 and 445d534.

📒 Files selected for processing (1)

• .github/workflows/docs.yml

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}