Skip to content

Rebuild

Rebuild #2258

Triggered via schedule May 2, 2026 01:54
Status Failure
Total duration 8m 24s
Artifacts 2

rebuild.yaml

on: schedule
Matrix: Rebuild
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 4 warnings
Rebuild (3.28, 3.11)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
Rebuild (3.28, 3.11)
Process completed with exit code 2.
Rebuild (3.30, 3.11)
Critical vulnerability found by Snyk in the published image: camptocamp/mapfish_print:3.30.
Rebuild (3.30, 3.11)
Critical vulnerability found by Snyk in the published image: ghcr.io/camptocamp/mapfish_print:3.30.
Rebuild (3.28, 3.11)
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-python@v5, 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/
Rebuild (3.29, 3.11)
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-python@v5. 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/
Rebuild (3.30, 3.11)
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-python@v5. 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/
Rebuild (3.30, 3.11)
print_version: twine: no present: Command '['twine', '--version']' returned non-zero exit status 1.

Artifacts

Produced during runtime
Name Size Digest
Reports core Expired
340 KB
sha256:fbe9ce03dfa6ccf1f9c375e6656149e417009ae4f6a201d3022180fe4f324af2
Test results Expired
4.72 KB
sha256:18f8632558ee9ac52a4e3e33f71baf3f4a9ab7f7c761b913bdee816ee94c69db