Skip to content

Merge pull request #738 from SprocketBot/cursor/issue-726-org-team-pe… #1046

Merge pull request #738 from SprocketBot/cursor/issue-726-org-team-pe…

Merge pull request #738 from SprocketBot/cursor/issue-726-org-team-pe… #1046

Triggered via push April 14, 2026 03:16
Status Success
Total duration 4m 11s
Artifacts 23

on-changes.yml

on: push
Build base docker image
2m 2s
Build base docker image
Matrix: Build Node Services
Merge container BOM (main)
9s
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 (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 (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 (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 (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 (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/
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/
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/
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 (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/
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/
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/
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 (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 (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~2Q9KTB.dockerbuild
91.1 KB
sha256:b46febc303e768735a7c1c6a4878ba455d2967755d41bf8d5c95ce56415cfc28
SprocketBot~sprocket~5TB7EE.dockerbuild
56.1 KB
sha256:1e564bb67bb0bcdbce25b94d5172c7fc2a9bf701130d36cc8cc5134c8e1a30bb
SprocketBot~sprocket~JHLLXJ.dockerbuild
56.2 KB
sha256:8fe4279463e345d7d56a2677c24dd64a1fa3b5d003fdadd2940b18c640077677
SprocketBot~sprocket~N4MQ4A.dockerbuild
56.3 KB
sha256:b47d9be51beb3be533bc351047c5e4cad92869aef3314185d7ccc4aae07f012a
SprocketBot~sprocket~N6IKOY.dockerbuild
60 KB
sha256:9b316c541d9ab9c9d6d994b426f5690b4310daa058f7095ed5868c81f148b754
SprocketBot~sprocket~NRK7RA.dockerbuild
56.6 KB
sha256:ce0eac70e4c79258545c2611d15301971f74e70351e1e6bfb02cf0bbc226fc8d
SprocketBot~sprocket~OUPTZE.dockerbuild
56.8 KB
sha256:b8e670b6711cebfc4ff3062ce639101a266f9efe2d2d26c4ec641c9b0d951110
SprocketBot~sprocket~R900P3.dockerbuild
56.7 KB
sha256:0629e8dac0911e79adab3fafc95cda208c3722460ad4f459fad4e3eff4445ca1
SprocketBot~sprocket~RREOKB.dockerbuild
57.9 KB
sha256:5d5d7f687bd7789f6c3e58ac65ef1a931c26c06006d55a444825da80612b5752
SprocketBot~sprocket~SCECXY.dockerbuild
59.6 KB
sha256:5ea81387fdd19917f42f77e24a7c1683ad0ec7faef75ea51a4b03054505f007e
SprocketBot~sprocket~YBUDS1.dockerbuild
56.8 KB
sha256:c3347c3680ab8f4f4576e207e7c3f38a3c035f431bbbf7502e362c6a2e523492
bom-fragment-core
277 Bytes
sha256:0b3c477f42531bc9e0d612312a51838c552f9b3cb151d2364d01899119121741
bom-fragment-discord-bot
298 Bytes
sha256:9c23060392343c710a9e493452677d16f18bb88d44a2cbcd274400d742820155
bom-fragment-image-generation-frontend
332 Bytes
sha256:81dc453b67a86953a5223f388649928d75a98a7289fa084f31af1cac12503939
bom-fragment-image-generation-service
329 Bytes
sha256:609091885cd693a3a8ad24ea410cb68f2ac281622a90abda55058e6f002f770a
bom-fragment-matchmaking-service
317 Bytes
sha256:0233896205689cdc193b403548f261d6ef21a9575f2b41565a3b7c5c799ae2bf
bom-fragment-monorepo-core
301 Bytes
sha256:803822ef5d2295b6c5b67754b9c785bb197ff7bfe8830b7c8c333b2184ae554a
bom-fragment-notification-service
323 Bytes
sha256:82156b29baa71839b845643169a1907dbf82ff3d09ab7b0e0aec577b98c61c8f
bom-fragment-replay-parse-service
323 Bytes
sha256:efaf5d3c437cf07b8f1df1d3d4fd2772e0a8856ab13a7f5f3d2ce9c11e6c4221
bom-fragment-server-analytics-service
332 Bytes
sha256:32edccb4b700fd7d8a9437f5ed793d5a53b77261575b6bde469844be9379b536
bom-fragment-submission-service
315 Bytes
sha256:b596203e0fb0e1ca1abae0bb7c373194d9ad8ee8928d12773f0c37db5b2d2049
bom-fragment-web
273 Bytes
sha256:b05996e05cba7dadddc18bbc25d372812cb486c6f010596eb2c3aee247eba51c
bom-main
937 Bytes
sha256:6630a2d083d876dd2b0f7bfb7343ac0837987e00a78ae1ad86de064893d2bbd5