Upgrade GitHub Actions to Node.js 24-compatible versions

[Copilot]

Node.js 20 is deprecated on GitHub Actions runners with forced migration to Node.js 24 starting June 2, 2026. All workflow files need action versions that run on Node.js 24.

Action version upgrades (all workflows)

• actions/checkout@v4 → v5
• actions/setup-node@v4 → v6
• actions/github-script@v7 → v8 (extension-submission.yml, discover-templates-extensions.yml)
• actions/upload-pages-artifact@v3 → v4 (release.yml)

Node.js version

• node-version: 20 → 24 across all workflows
• website/package.json engines.node: >=20.0 → >=24.0

Original prompt

---

This section details on the original issue you should resolve

<issue_title>update action in release yml</issue_title>
<issue_description>Warning message: "Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, peaceiris/actions-gh-pages@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/"

1. Update all actions in yml to latest version and verify which node version is required.
2. Update to the highest node version that is compatible to all actions in yml. </issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes update action in release yml #772

---

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.

[hemarina]

@copilot Update website/package-lock.json based on website/package.json

[Copilot]

@copilot Update website/package-lock.json based on website/package.json

Done in 951be32. Ran npm install in the website/ directory to regenerate package-lock.json — the engines.node entry is now updated from >=20.0 to >=24.0.