Skip to content

chore(main): release 1.9.19 #886

chore(main): release 1.9.19

chore(main): release 1.9.19 #886

Triggered via pull request April 12, 2026 22:02
Status Success
Total duration 2m 38s
Artifacts 1

docker-release.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

11 warnings
docker-build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, docker/metadata-action@c1e51972afc2121e065aed6d45c65596fe445f3f, docker/setup-buildx-action@e468171a9de216ec08956ac3ada2f0791b6bd435. 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/
Variables should be defined before their use: Dockerfile#L41
UndefinedVar: Usage of undefined variable '$DATABASE_URL' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L40
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L39
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Sensitive data should not be used in the ARG or ENV commands: Dockerfile#L38
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "DISCORD_TOKEN") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
Variables should be defined before their use: Dockerfile#L38
UndefinedVar: Usage of undefined variable '$DISCORD_TOKEN' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L1
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
Variables should be defined before their use: Dockerfile#L43
UndefinedVar: Usage of undefined variable '$HOSTNAME' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L42
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L41
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Variables should be defined before their use: Dockerfile#L40
UndefinedVar: Usage of undefined variable '$DISCORD_DEV_GUILD_ID' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Artifacts

Produced during runtime
Name Size Digest
LEDBrain~Community-Service~QJ0Q0P.dockerbuild
94.3 KB
sha256:fb85415ae03f6645fb973a3e0e52b4f5410489ebf4465764e73ae422d434e182