fix: handle cannot_reply_to_message error in slack agent (#1991) #44
thibaultleouaydocker-publish.yml
on: push
prepare
8s
Matrix: build-and-push
Annotations
7 errors and 7 warnings
|
build-and-push (checker, apps/checker, apps/checker/Dockerfile)
Canceling since a higher priority waiting request for docker-refs/heads/main exists
|
|
build-and-push (checker, apps/checker, apps/checker/Dockerfile)
The operation was canceled.
|
|
build-and-push (dashboard, ., apps/dashboard/Dockerfile)
Canceling since a higher priority waiting request for docker-refs/heads/main exists
|
|
build-and-push (dashboard, ., apps/dashboard/Dockerfile)
The operation was canceled.
|
|
build-and-push (status-page, ., apps/status-page/Dockerfile)
Canceling since a higher priority waiting request for docker-refs/heads/main exists
|
|
build-and-push (status-page, ., apps/status-page/Dockerfile)
The operation was canceled.
|
|
Publish Docker Images
Canceling since a higher priority waiting request for docker-refs/heads/main exists
|
|
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. 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, anchore/sbom-action@v0, 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. 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, ., apps/workflows/Dockerfile)
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, anchore/sbom-action@v0, 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. 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, apps/private-location, apps/private-location/Dockerfile)
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, anchore/sbom-action@v0, 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. 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, apps/checker, apps/checker/Dockerfile)
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. 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, ., apps/dashboard/Dockerfile)
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. 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 (status-page, ., apps/status-page/Dockerfile)
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. 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~EP11KU.dockerbuild
|
88 KB |
sha256:ea200a8e412f283509d0537920e41f36a7ec09475b7d8691046b1845695fc86f
|
|
|
openstatusHQ~openstatus~K4K6AD.dockerbuild
|
708 KB |
sha256:89f985da600634b4c569de0598e8532cbd3dcdaf9daca3ab56e1e129909a0016
|
|
|
openstatusHQ~openstatus~TJGRZ0.dockerbuild
|
380 KB |
sha256:5ee46709cdc22216ad4db92648f559c100087d7e3fdc3d3413a6a3a5a120770c
|
|
|
openstatushq-openstatus-private-location_sha256_65fd774296258d985b5bcb94d770475a49f258a00f7910aac917842b32be37bc.spdx.json
|
17.2 KB |
sha256:22db6380abbd4db71a5ebe8a9e6794c13bd584271dc651417f99fd08773b38cf
|
|
|
openstatushq-openstatus-server_sha256_e5ec24ac281733b9a4ba6ced6e410498e33588d095a04c46accf70f06a7fb21b.spdx.json
|
389 KB |
sha256:818eee24fa74113ff891d47be32a7041f00009e2b605209ac7d8bbf379ba975f
|
|
|
openstatushq-openstatus-workflows_sha256_bd852064b0a0171f088d4bf9c46395f5498d7b84630a3822c700fb6271708784.spdx.json
|
420 KB |
sha256:5263d62feeea61aa5aa2f572ffa057e98128042af4c0136ec498fb391f0d54b6
|
|
|
sbom-private-location
|
17 KB |
sha256:140dc288504bc3f467f1035de15b71ceb8ade4c2bb4c53889c68109861dc3162
|
|
|
sbom-server
|
389 KB |
sha256:27988c8861dd9b3dd2f137b20cae64904374f7c450cd615060ca5f7df72f0f92
|
|
|
sbom-workflows
|
420 KB |
sha256:2064c5b35cdb1afe9d511072bb37511b2dcf5bb973a09bffefb7e901f7ee8b90
|
|