ZAD deployment: containers, CI/CD, runtime config #2
Annotations
1 error and 4 warnings
|
build-frontend
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c chmod g+w /usr/share/nginx/html" did not complete successfully: exit code: 1
|
|
generate-sources
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5, actions/upload-artifact@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/
|
|
generate-sources
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
|
build-backend
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5. 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/
|
|
build-frontend
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5. 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 | |
|---|---|---|---|
|
MinBZK~par-dpia-form~NLTXPU.dockerbuild
|
22.5 KB |
sha256:2b05ca575a651df32d780eabe82ac2f19c3faed98d1cd76c7cf3c94513170212
|
|
|
MinBZK~par-dpia-form~TCUC2O.dockerbuild
|
21.5 KB |
sha256:ffd7fd54036ef1c758ef55a682a48971539e5bee039f5225e8ed8b87a31c1383
|
|
|
generated-sources
Expired
|
67.9 KB |
sha256:bf4c9d0f5f60e0b62f5c798f724fa603529b139cb56f071296ead9de049c32cd
|
|