Skip to content

fix: re-encrypt dev Pulumi stack config #1050

fix: re-encrypt dev Pulumi stack config

fix: re-encrypt dev Pulumi stack config #1050

Triggered via push April 14, 2026 04:27
Status Success
Total duration 4m 19s
Artifacts 23

on-changes.yml

on: push
Build base docker image
2m 9s
Build base docker image
Matrix: Build Node Services
Merge container BOM (main)
8s
Merge container BOM (main)
Fit to window
Zoom out
Zoom in

Annotations

35 warnings
Build base docker image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@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/
The 'as' keyword should match the case of the 'from' keyword: dockerfiles/node.Dockerfile#L1
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
Build Node Services (submission-service, ./microservices/submission-service)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@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/
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals: microservices/submission-service/Dockerfile#L6
JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
Default value for global ARG results in an empty or invalid base image name: microservices/submission-service/Dockerfile#L2
InvalidDefaultArgInFrom: Default value for ARG $BASE_IMAGE results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
Build Node Services (matchmaking-service, ./microservices/matchmaking-service)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@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/
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals: microservices/matchmaking-service/Dockerfile#L6
JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
Default value for global ARG results in an empty or invalid base image name: microservices/matchmaking-service/Dockerfile#L2
InvalidDefaultArgInFrom: Default value for ARG $BASE_IMAGE results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
Build Node Services (server-analytics-service, ./microservices/server-analytics-service)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@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/
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals: microservices/server-analytics-service/Dockerfile#L6
JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
Default value for global ARG results in an empty or invalid base image name: microservices/server-analytics-service/Dockerfile#L2
InvalidDefaultArgInFrom: Default value for ARG $BASE_IMAGE results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
Build Node Services (discord-bot, ./clients/discord-bot)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@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/
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals: clients/discord-bot/Dockerfile#L7
JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
Default value for global ARG results in an empty or invalid base image name: clients/discord-bot/Dockerfile#L5
InvalidDefaultArgInFrom: Default value for ARG $BASE_IMAGE results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
Default value for global ARG results in an empty or invalid base image name: clients/discord-bot/Dockerfile#L2
InvalidDefaultArgInFrom: Default value for ARG $BASE_IMAGE results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
Build Node Services (image-generation-frontend, ./clients/image-generation-frontend)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@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/
Default value for global ARG results in an empty or invalid base image name: clients/image-generation-frontend/Dockerfile#L5
InvalidDefaultArgInFrom: Default value for ARG $BASE_IMAGE results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
Default value for global ARG results in an empty or invalid base image name: clients/image-generation-frontend/Dockerfile#L2
InvalidDefaultArgInFrom: Default value for ARG $BASE_IMAGE results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals: clients/image-generation-frontend/Dockerfile#L8
JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
Build Node Services (image-generation-service, ./microservices/image-generation-service)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@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/
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals: microservices/image-generation-service/Dockerfile#L8
JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
Default value for global ARG results in an empty or invalid base image name: microservices/image-generation-service/Dockerfile#L2
InvalidDefaultArgInFrom: Default value for ARG $BASE_IMAGE results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
Build Node Services (notification-service, ./microservices/notification-service)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@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/
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals: microservices/notification-service/Dockerfile#L6
JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
Default value for global ARG results in an empty or invalid base image name: microservices/notification-service/Dockerfile#L2
InvalidDefaultArgInFrom: Default value for ARG $BASE_IMAGE results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
Build Node Services (web, ./clients/web)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@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/
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals: clients/web/Dockerfile#L9
JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
Default value for global ARG results in an empty or invalid base image name: clients/web/Dockerfile#L6
InvalidDefaultArgInFrom: Default value for ARG $BASE_IMAGE results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
Default value for global ARG results in an empty or invalid base image name: clients/web/Dockerfile#L2
InvalidDefaultArgInFrom: Default value for ARG $BASE_IMAGE results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
Build Node Services (core, ./core)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@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/
Default value for global ARG results in an empty or invalid base image name: core/Dockerfile#L9
InvalidDefaultArgInFrom: Default value for ARG $BASE_IMAGE results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
Default value for global ARG results in an empty or invalid base image name: core/Dockerfile#L2
InvalidDefaultArgInFrom: Default value for ARG $BASE_IMAGE results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals: core/Dockerfile#L13
JSONArgsRecommended: JSON arguments recommended for ENTRYPOINT to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
Build Node Services (replay-parse-service, ./microservices/replay-parse-service)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@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/
Merge container BOM (main)
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, actions/upload-artifact@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/

Artifacts

Produced during runtime
Name Size Digest
SprocketBot~sprocket~4MU35I.dockerbuild
55.1 KB
sha256:5607ec92c52588713ff267036b1b240e0c90820228f5d38c1988ea8f78e2012f
SprocketBot~sprocket~746SW3.dockerbuild
59.6 KB
sha256:a068369070ae3b7f82d2c8fb3a5c5e5b272173e00c1170d0d912a2234fc78cb6
SprocketBot~sprocket~EF3EL3.dockerbuild
55.3 KB
sha256:4ce34e46e6e70c5149f298f96a7d1b327f7780b3c0662d08500772ac96fb2d79
SprocketBot~sprocket~GWJD3A.dockerbuild
55.2 KB
sha256:816a61c8afd084bc3659386410489f04de848bf54e3acdaf5650b51cc386b13f
SprocketBot~sprocket~JYWMK3.dockerbuild
58.5 KB
sha256:2de1cdcbd598edcf0a29ec8b31e6346c12c8db39e85c42e034cceccb1937bab5
SprocketBot~sprocket~KRYVFB.dockerbuild
54.9 KB
sha256:8e5bff7d396572af72c6525d7b94c11db57d4976df110724a9d7ae7d79a99862
SprocketBot~sprocket~N1P2GJ.dockerbuild
55 KB
sha256:da0d51839580bc20755698988a2b4bd782dbd3e8fa7fa263fafacb02c1c7c72f
SprocketBot~sprocket~NKWGFR.dockerbuild
55.8 KB
sha256:c0215b3e27b0bfbe07b349fa0d895628360a34c7095a9414b20d5c5378676ebd
SprocketBot~sprocket~NLLTBH.dockerbuild
55.4 KB
sha256:2f74c6ccecfcb4bbdb1266e2c2dcb009b3df8afe667bde6e86d083a2a95c5374
SprocketBot~sprocket~OZZIH9.dockerbuild
90.2 KB
sha256:08d7d1e5f4fe59d141e1f8f706eb79b0e590ae77c57d3c3e176927baa323381d
SprocketBot~sprocket~TNEOKF.dockerbuild
57.6 KB
sha256:6ee6a04fe8ca92987abf80090315508539ff652265ad1b3558ef972cbeeb8697
bom-fragment-core
278 Bytes
sha256:510be6e4d164a38175cc7d2b4d4e9a3a05c561b68d94357b93e58135e7ef97d0
bom-fragment-discord-bot
298 Bytes
sha256:119afc40a74ff6b59a11fa55540ae3655ec2da02eb077bbb4a3e05c879beb3ee
bom-fragment-image-generation-frontend
335 Bytes
sha256:92436157c460fa8663b5a36444051d36a85b5059e27202354b05b32e6235e740
bom-fragment-image-generation-service
333 Bytes
sha256:79a6f2872ad57c5d126457b7f52b2d9cba0a4d62a9d69d383615d2528253c16a
bom-fragment-matchmaking-service
319 Bytes
sha256:dd721fb3b7926265d71de32309c744709dfe8d79d32d0ed49b2fe1cb52b17cdb
bom-fragment-monorepo-core
303 Bytes
sha256:5fc536dd3b025c6073f5a34b4e851baf27087a1d18afcfdd94cdef1504091fbe
bom-fragment-notification-service
322 Bytes
sha256:5fd808b6fe64a1e9a8341a894134517149d66f12525e60241d7c58534ce9da38
bom-fragment-replay-parse-service
324 Bytes
sha256:1452e0ab6206b2bb59a853d967c5ec17bbeca0d0770c28cb95c76f2dfa307c2a
bom-fragment-server-analytics-service
332 Bytes
sha256:b923ad0dfc979b29e1818960cfca32f86ffdea05ad33359e6d0a91e065b668f5
bom-fragment-submission-service
317 Bytes
sha256:dc492262bb8817e391d663e289638fcf6247517046ebdc9e390856e301b95bcf
bom-fragment-web
274 Bytes
sha256:d32ac44f5b3cfac6576f1dd838fdeb70a5d6ac12842088a737ccaf7d0192a603
bom-main
934 Bytes
sha256:f8d317d3ebf8f44d3a2772a9a0424e1e6652ce45f603cc7cd6a4d05222b686c5