fix: csp headers #13
aggmoulikdocker-publish.yml
on: push
prepare
8s
Matrix: build-and-push
Annotations
2 errors and 18 warnings
|
build-and-push (dashboard, ., apps/dashboard/Dockerfile)
The job has exceeded the maximum execution time of 30m0s
|
|
build-and-push (dashboard, ., apps/dashboard/Dockerfile)
The operation was canceled.
|
|
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 (server, ., apps/server/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, 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, ., 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, 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, 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, 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 (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, 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, 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/
|
|
Sensitive data should not be used in the ARG or ENV commands:
apps/status-page/Dockerfile#L10
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "UNKEY_TOKEN")
More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
|
|
Sensitive data should not be used in the ARG or ENV commands:
apps/status-page/Dockerfile#L10
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "OPENPANEL_CLIENT_SECRET")
More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
|
|
Sensitive data should not be used in the ARG or ENV commands:
apps/status-page/Dockerfile#L10
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "RESEND_API_KEY")
More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
|
|
Variables should be defined before their use:
apps/status-page/Dockerfile#L10
UndefinedVar: Usage of undefined variable '$PNPM_HOME'
More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
|
|
Sensitive data should not be used in the ARG or ENV commands:
apps/status-page/Dockerfile#L10
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "DATABASE_AUTH_TOKEN")
More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
|
|
Sensitive data should not be used in the ARG or ENV commands:
apps/status-page/Dockerfile#L10
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "VERCEL_AUTH_BEARER_TOKEN")
More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
|
|
Sensitive data should not be used in the ARG or ENV commands:
apps/status-page/Dockerfile#L10
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "UPSTASH_REDIS_REST_TOKEN")
More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
|
|
Sensitive data should not be used in the ARG or ENV commands:
apps/status-page/Dockerfile#L10
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "TINY_BIRD_API_KEY")
More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
|
|
Sensitive data should not be used in the ARG or ENV commands:
apps/status-page/Dockerfile#L10
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "STRIPE_SECRET_KEY")
More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
|
|
Sensitive data should not be used in the ARG or ENV commands:
apps/status-page/Dockerfile#L10
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "CRON_SECRET")
More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
|
|
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. 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 | |
|---|---|---|---|
|
aggmoulik-openstatus-checker_sha256_48562ff6ac866b38820f0d37a3a3ff7916ad9bc31a639f9dd887fc08140c267a.spdx.json
|
8.68 KB |
sha256:350575ac814ad3f382fe3e377dc45dd2704f0e6986efe369ecc2f9cb14f2050e
|
|
|
aggmoulik-openstatus-private-location_sha256_2c0102bf36ab446a0116d203ec038a5d6ac2e1ca64327446c341415ac70d8dda.spdx.json
|
17.2 KB |
sha256:06d533a634271b928687056fe750e2c45bbb7bac960744322bc7f5779e19b5e0
|
|
|
aggmoulik-openstatus-server_sha256_cc6b0a76c9e702ce53b83fe82808c73f50231f9b64d6f0a1cf88de4650573c18.spdx.json
|
389 KB |
sha256:c341bb8b21086a89910e1dd4c2ddbe8cc9cd92282acdb16dde8edaafb47b7938
|
|
|
aggmoulik-openstatus-status-page_sha256_9ef4c4f550bd4fcc1f1f3329711c641eb3af052fd1672627cafc15db5995c06f.spdx.json
|
997 KB |
sha256:fd7faa415f078bf239b304bcb34972d29f8664348af7217ea4cd4556393b22f0
|
|
|
aggmoulik-openstatus-workflows_sha256_e863bdfefad1cf1ee3ecad609cf6c147e35f49216865f37160c8607049292be1.spdx.json
|
420 KB |
sha256:3ee7a34e8580e7ac36137c25668df5b95d5cbc1e8502fe1936102f69f1e57e12
|
|
|
aggmoulik~openstatus~BO0BSH.dockerbuild
|
711 KB |
sha256:05230c841c1d189bea6bc5f38452ddfb9c2b672c1eff43c5d2aaa88810026f60
|
|
|
aggmoulik~openstatus~MHBNP4.dockerbuild
|
738 KB |
sha256:a4dd2cd59cd3d1d93adb4af72538bffab138b125b140d6a43a1ffab29f928246
|
|
|
aggmoulik~openstatus~Q7PS04.dockerbuild
|
93.4 KB |
sha256:63364b8d762dd658af3d0c7870d7d982d2bf11248c3173adf78aa28fbb420044
|
|
|
aggmoulik~openstatus~QCSZYN.dockerbuild
|
88 KB |
sha256:23ad1138bedcf0297d2dddb6fc68d55811d3bb7eec475daffdeffa309bedfe7b
|
|
|
aggmoulik~openstatus~SODNNL.dockerbuild
|
128 KB |
sha256:e5102800d84667c00d69fbd8e65cf9db8325d01cd794d10d9ac21ddaa71a1ad5
|
|
|
sbom-checker
|
8.51 KB |
sha256:ba428d995ceb18a15a14aede84c763e3661ef839509d3f01b2f58c378c1ec84c
|
|
|
sbom-private-location
|
17.1 KB |
sha256:858c7e319dcf16240afb476733d347077655bd4c53ab23dac9f6d4c53ed25665
|
|
|
sbom-server
|
389 KB |
sha256:7856f46618e66d68d3611384561d5279b4af8236ea8a3571b392642f43a09c4b
|
|
|
sbom-status-page
|
997 KB |
sha256:0f61be054990d5fb305418a37d66dd8d068689463cb5312791d9520bb915baba
|
|
|
sbom-workflows
|
420 KB |
sha256:d78de55c48659c8c5634b671f8dd274df0fab360f55824b6e9aea5e59428e5ea
|
|