feat: bug delete user (#2196) #177
thibaultleouaydocker-publish.yml
on: push
prepare
9s
Matrix: build-and-push
Annotations
2 errors and 8 warnings
|
build-and-push (status-page)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c corepack enable\npnpm install --frozen-lockfile\npnpm turbo run build --filter=@openstatus/status-page\n" did not complete successfully: exit code: 1
|
|
build-and-push (dashboard)
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c corepack enable\npnpm install --frozen-lockfile\npnpm turbo run build --filter=@openstatus/dashboard\n" did not complete successfully: exit code: 1
|
|
prepare
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 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/
|
|
build-and-push (checker)
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, docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. 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/
|
|
The 'as' keyword should match the case of the 'from' keyword:
apps/checker/Dockerfile#L1
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
|
build-and-push (status-page)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. 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/
|
|
build-and-push (dashboard)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. 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/
|
|
build-and-push (server)
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, docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. 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/
|
|
build-and-push (workflows)
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, docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. 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/
|
|
build-and-push (private-location)
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, docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. 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 | |
|---|---|---|---|
|
openstatusHQ~openstatus~E6UI2O.dockerbuild
|
43.3 KB |
sha256:dbb07f57a24ecd9e42deae62584bf169c7eba7be10fef38d0a1555b46d7c6203
|
|
|
openstatusHQ~openstatus~I6IQRO.dockerbuild
|
56.5 KB |
sha256:d87955d5ccbfefacd4bc885cb19233bbfd785db0f59715e793e8b418fbfafde8
|
|
|
openstatusHQ~openstatus~JVSF23.dockerbuild
|
154 KB |
sha256:8d8a862386c2f31ca22e4132fa8739efd1595a9b0974c7c0707b84dbf9239347
|
|
|
openstatusHQ~openstatus~NNUBHQ.dockerbuild
|
43.3 KB |
sha256:73f894fab9682dae0199c5cf6672086262b22ae6c2c10d7d2a880829f1d677df
|
|
|
openstatusHQ~openstatus~SZ7Z97.dockerbuild
|
128 KB |
sha256:874b47ec5a559a2705eecd45451438f858177c7ee21bb6df0bf81d4143706e41
|
|
|
openstatusHQ~openstatus~VXH26A.dockerbuild
|
93.6 KB |
sha256:dc82785d09465a50ceed357405c0d10669c4a7f2e771bf307ed8e77c4397177f
|
|
|
openstatushq-openstatus-checker_sha256_8f62c3c2e926252edb4115982c1a308789dfcea73bb37dbe7a74e0b387a468f0.spdx.json
|
8.7 KB |
sha256:4f24ffb06ae423f1d6392bab7060047d25b07c240237d30d2a5fdb857e08a8e7
|
|
|
openstatushq-openstatus-private-location_sha256_f4ae49fcacd85ab335478a4b01ef003d24b1f30108b005eaaf1bf2bf1c19896f.spdx.json
|
17.2 KB |
sha256:005896ae3db866acf92280386fa8f2ffbd0ded83b1dec1b3f2cde52554e38630
|
|
|
openstatushq-openstatus-server_sha256_bc53110f3f166bd43b98bb96b468681934f74cbb93874443a5cb019f748b8a67.spdx.json
|
389 KB |
sha256:cdaec26e79b9378e252c816fa167c1626ae2d3aaf83bc0bc78a374bb9933ec34
|
|
|
openstatushq-openstatus-workflows_sha256_c61d12b75106dce6f827a38b28f2ce38a05e7794c6441511d6e89147264156b2.spdx.json
|
420 KB |
sha256:5fc8f7a1bbc88efa295bea51441d5899052f5ea6a4ae5f7e581fd589fe688173
|
|
|
sbom-checker
Expired
|
8.52 KB |
sha256:594ea85ace3cfcd00d9376cbad8e9ec427b306a961c710df6389f0d3146c7ad9
|
|
|
sbom-private-location
Expired
|
17 KB |
sha256:d959587d822fc6773f4d3500b7c1d49db77b61350821d0146f1f3e129687f407
|
|
|
sbom-server
Expired
|
389 KB |
sha256:96214d0c07408691658e0f85bd6054d2ee7d78b715d71525a8a9453cac5950a2
|
|
|
sbom-workflows
Expired
|
420 KB |
sha256:1225d8832c567776dde6ac492d964399717ee1aff178cd704a5c141b432f4f14
|
|