Skip to content

ci: replace built-in pages workflow with Node.js 24-compatible actions#436

Open
gkorland wants to merge 1 commit intomainfrom
ci/update-pages-actions-node24
Open

ci: replace built-in pages workflow with Node.js 24-compatible actions#436
gkorland wants to merge 1 commit intomainfrom
ci/update-pages-actions-node24

Conversation

@gkorland
Copy link
Copy Markdown
Contributor

Summary

Replace the GitHub-managed pages-build-deployment workflow with a custom Jekyll deploy workflow that uses Node.js 24-compatible action versions, eliminating the Node.js 20 deprecation warning.

Changes

  • Add .github/workflows/pages.yml — custom GitHub Pages deploy workflow
  • All actions pinned to full commit SHAs (security best practice):
    • actions/checkout@v6.0.2 — Node.js 24 runtime (was @v4 / Node.js 20)
    • actions/configure-pages@v6.0.0
    • actions/jekyll-build-pages@v1.0.13 (unchanged)
    • actions/upload-pages-artifact@v5.0.0 (replaces upload-artifact@v4)
    • actions/deploy-pages@v5.0.0

Testing

The new workflow will trigger on merge to main. It replicates the exact steps of the built-in pages-build-deployment workflow using up-to-date actions.

Note: After merging, verify in Settings → Pages that the deployment source is the new custom workflow. The built-in workflow may need to be disabled from there if both run simultaneously.

Memory / Performance Impact

N/A

Related Issues

Fixes Node.js 20 deprecation warning:

Node.js 20 actions are deprecated. The following actions are running on Node.js 20: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026.

Add custom Jekyll deploy workflow using action versions that run on
Node.js 24, replacing the GitHub-managed pages-build-deployment
workflow which used deprecated Node.js 20 actions.

Action versions updated:
- actions/checkout: v4 → v6.0.2 (node24)
- actions/configure-pages: → v6.0.0
- actions/jekyll-build-pages: v1.0.13 (unchanged)
- actions/upload-pages-artifact: → v5.0.0
- actions/deploy-pages: → v5.0.0

Resolves Node.js 20 deprecation warning on pages build and deployment.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Apr 21, 2026

Warning

Rate limit exceeded

@gkorland has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 16 minutes and 28 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 16 minutes and 28 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 24831212-e00e-47ed-b031-33a902aae8f4

📥 Commits

Reviewing files that changed from the base of the PR and between dde8338 and c354318.

📒 Files selected for processing (1)
  • .github/workflows/pages.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch ci/update-pages-actions-node24

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

Comment @coderabbitai help to get the list of available commands and usage tips.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant