Fixes the build with duplicate versions #330
ci.yml
on: push
build-job
13m 30s
deploy-job
19s
Annotations
10 errors and 2 warnings
|
build-job
Unable to query cache: Error: Cache service responded with 400
|
|
build-job
Unable to query cache: Error: Cache service responded with 400
|
|
build-job
Unable to query cache: Error: Cache service responded with 400
|
|
build-job
Unable to query cache: Error: Cache service responded with 400
|
|
build-job
Unable to query cache: Error: Cache service responded with 400
|
|
build-job
Unable to query cache: Error: Cache service responded with 400
|
|
build-job
Unable to query cache: Error: Cache service responded with 400
|
|
build-job
Unable to query cache: Error: Cache service responded with 400
|
|
build-job
Unable to query cache: Error: Cache service responded with 400
|
|
build-job
Unable to query cache: Error: Cache service responded with 400
|
|
build-job
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/configure-pages@v5, actions/setup-node@v4, actions/upload-artifact@v4, rharkor/caching-for-turbo@v1.5. 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/
|
|
deploy-job
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/deploy-pages@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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
github-pages
Expired
|
212 MB |
sha256:acfa8082c0c202b4508e9a32b405e2191a5ce51be2a588184b2b6e88f282943b
|
|