ci(website): move Pages deploy to Node 24 actions and runtime

[frbrkoala]

The first-party Pages deploy failed ("Deployment failed, try again later") and warned that configure-pages@v5 / upload-artifact@v4 target the deprecated Node 20 and were force-run on Node 24. Move the website workflows off Node 20:

• actions/configure-pages v5 -> v6
• actions/upload-pages-artifact v3 -> v5
• actions/deploy-pages v4 -> v5
• setup-node node-version 20 -> 24 in both website-deploy.yaml and website-test-deploy.yml

Node 24 is the current active LTS and the version the site build was verified on locally. This clears the Node 20 deprecation warning and moves deploy-pages onto a Node 24-compatible release. A lingering "try again later" is a transient/wedged Pages deploy and clears on a workflow re-run.

What does this PR do?

🛑 Please open an issue first to discuss any significant work and flesh out details/direction — we would hate for your time to be wasted.
Consult the CONTRIBUTING guide for submitting pull-requests.

Motivation

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• New blueprint (adding a new protocol — see checklist below)
• Documentation update
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Testing

• I have run npm run build successfully
• I have run npm run test and all tests pass
• I have run npx cdk synth with a sample .env (e.g. from blueprints/dummy/samples/) and it succeeds
• I have run pre-commit hooks: npm run run-pre-commit

New Blueprint Checklist (if adding a protocol)

• Blueprint follows the structure of blueprints/dummy/ (reference implementation)
• Blueprint README follows the standard template (matches Dummy section titles and ordering)
• Setup section points to Getting Started (not inline instructions)
• Deployment section leads with AI-driven deployment (Option 1) and manual as Option 2
• Sample .env files are provided for at least one network (mainnet or testnet)
• Configuration scripts follow the install/run dispatch pattern (see blueprints/dummy/)
• Blueprint page added to website/docs/blueprints/ (.mdx mirror importing README)
• Client Release Channels table added to README under Additional Resources

Documentation

• I have updated relevant documentation (if applicable)
• I have run cd website && npm run build with no broken links (if docs changed)

License

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[github-actions]

Dependency Review

The following issues were found:

• ✅ 0 vulnerable package(s)
• ✅ 0 package(s) with incompatible licenses
• ✅ 0 package(s) with invalid SPDX license definitions
• ⚠️ 3 package(s) with unknown licenses.

See the Details below.

License Issues

.github/workflows/website-deploy.yaml

Package	Version	License	Issue Type
actions/configure-pages	6.*.*	Null	Unknown License
actions/deploy-pages	5.*.*	Null	Unknown License
actions/upload-pages-artifact	5.*.*	Null	Unknown License

OpenSSF Scorecard

Package	Version	Score	Details
actions/actions/configure-pages	6.*.*	🟢 6.1	Details Check Score Reason Code-Review 🟢 10 all changesets reviewed Maintained ⚠️ 0 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Binary-Artifacts 🟢 10 no binaries found in the repo Packaging ⚠️ -1 packaging workflow not detected CII-Best-Practices ⚠️ 0 no effort to earn an OpenSSF best practices badge detected Token-Permissions ⚠️ 0 detected GitHub workflow tokens with excessive permissions Pinned-Dependencies 🟢 6 dependency not pinned by hash detected -- score normalized to 6 License 🟢 10 license file detected Fuzzing ⚠️ 0 project is not fuzzed Signed-Releases ⚠️ -1 no releases found Security-Policy 🟢 9 security policy file detected SAST 🟢 7 SAST tool detected but not run on all commits Branch-Protection 🟢 8 branch protection is not maximal on development and all release branches
actions/actions/deploy-pages	5.*.*	🟢 5.4	Details Check Score Reason Code-Review 🟢 10 all changesets reviewed Binary-Artifacts 🟢 10 no binaries found in the repo Maintained ⚠️ 0 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Packaging ⚠️ -1 packaging workflow not detected CII-Best-Practices ⚠️ 0 no effort to earn an OpenSSF best practices badge detected Token-Permissions ⚠️ 0 detected GitHub workflow tokens with excessive permissions Pinned-Dependencies 🟢 6 dependency not pinned by hash detected -- score normalized to 6 License 🟢 10 license file detected Signed-Releases ⚠️ -1 no releases found Fuzzing ⚠️ 0 project is not fuzzed Security-Policy 🟢 9 security policy file detected SAST 🟢 7 SAST tool detected but not run on all commits Branch-Protection ⚠️ 1 branch protection is not maximal on development and all release branches
actions/actions/upload-pages-artifact	5.*.*	🟢 5.8	Details Check Score Reason Code-Review 🟢 10 all changesets reviewed Maintained 🟢 3 4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3 Packaging ⚠️ -1 packaging workflow not detected Binary-Artifacts 🟢 10 no binaries found in the repo Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Token-Permissions ⚠️ 0 detected GitHub workflow tokens with excessive permissions Pinned-Dependencies 🟢 3 dependency not pinned by hash detected -- score normalized to 3 CII-Best-Practices ⚠️ 0 no effort to earn an OpenSSF best practices badge detected Fuzzing ⚠️ 0 project is not fuzzed License 🟢 10 license file detected Signed-Releases ⚠️ -1 no releases found Security-Policy 🟢 9 security policy file detected SAST ⚠️ 0 SAST tool is not run on all commits -- score normalized to 0 Branch-Protection 🟢 8 branch protection is not maximal on development and all release branches

Scanned Files

• .github/workflows/website-deploy.yaml

[github-actions]

Scan for commit: 35c3180 | Updated: 2026-07-06 03:34:12 UTC

🔒 Security Scan Results

Scanned files: 2

⚠️ Security findings detected. Please review and address before merging.