Skip to content

pages build and deployment #552

pages build and deployment

pages build and deployment #552

Triggered via GitHub Pages May 20, 2026 14:03
Status Failure
Total duration 2m 37s
Artifacts

pages-build-deployment

on: dynamic
report-build-status
3s
report-build-status
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 1 warning
deploy
Error: No artifacts named "github-pages" were found for this workflow run. Ensure artifacts are uploaded with actions/upload-artifact@v4 or later.
deploy
Error: No artifacts named "github-pages" were found for this workflow run. Ensure artifacts are uploaded with actions/upload-artifact@v4 or later. at getArtifactMetadata (/home/runner/work/_actions/actions/deploy-pages/v5/src/internal/api-client.js:85:1) at processTicksAndRejections (node:internal/process/task_queues:104:5) at Deployment.create (/home/runner/work/_actions/actions/deploy-pages/v5/src/internal/deployment.js:65:1) at main (/home/runner/work/_actions/actions/deploy-pages/v5/src/index.js:30:1)
deploy
Fetching artifact metadata failed. Is githubstatus.com reporting issues with API requests, Pages, or Actions? Please re-run the deployment at a later time.
build
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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/