Skip to content

Fix issue running uv sync #99

Fix issue running uv sync

Fix issue running uv sync #99

Triggered via push March 20, 2026 10:58
Status Failure
Total duration 1m 55s
Artifacts 2

Prebuild.yaml

on: push
Fit to window
Zoom out
Zoom in

Annotations

1 error and 2 warnings
Production
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c if [ -f requirements.txt ]; then echo \"requirements.txt found, installing dependencies with uv pip\" && uv venv .venv --clear && uv pip install -r requirements.txt; else echo \"Using uv sync for dependency installation\" && uv sync --locked --no-dev; fi" did not complete successfully: exit code: 1
Production
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, aws-actions/configure-aws-credentials@v4, docker/build-push-action@v6, docker/metadata-action@v4. 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/
Development
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, aws-actions/configure-aws-credentials@v4, docker/build-push-action@v6, docker/metadata-action@v4. 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/

Artifacts

Produced during runtime
Name Size Digest
diploi~component-fastapi~QG1B7P.dockerbuild
83.4 KB
sha256:c2842c51c3c6592a9376b20b2a5621f20b1f39828228755cd7b2830f67096654
diploi~component-fastapi~RQW1Z2.dockerbuild
12.8 KB
sha256:0b953b8fbc2cf79ba62ddf43be9fedd7a1edd70e30e19127cda9bf9542b308e2