Skip to content

Fix failed mention requests infinitely retrying (#432) #367

Fix failed mention requests infinitely retrying (#432)

Fix failed mention requests infinitely retrying (#432) #367

Triggered via push March 13, 2026 23:16
Status Success
Total duration 14m 24s
Artifacts 1
detect-changes
8s
detect-changes
user-feeds
0s
user-feeds
feed-requests
0s
feed-requests
monolith
14m 10s
monolith
bot-presence
bot-presence
discord-rest-listener
0s
discord-rest-listener
Fit to window
Zoom out
Zoom in

Annotations

7 warnings
detect-changes
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, dorny/paths-filter@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/
monolith
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/attest-build-provenance/predicate@36fa7d009e22618ca7cd599486979b8150596c74, actions/attest@67422f5511b7ff725f4dbd6fb9bd2cd925c65a8d, actions/checkout@v4, docker/build-push-action@v6, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-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/
Sensitive data should not be used in the ARG or ENV commands: services/backend-api/dockerfiles/web/mixed.Dockerfile#L29
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "VITE_PADDLE_CLIENT_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: services/backend-api/dockerfiles/web/mixed.Dockerfile#L28
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "VITE_PADDLE_PW_AUTH") 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: services/backend-api/dockerfiles/web/mixed.Dockerfile#L19
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "SENTRY_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: services/backend-api/dockerfiles/web/mixed.Dockerfile#L16
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "VITE_PADDLE_CLIENT_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: services/backend-api/dockerfiles/web/mixed.Dockerfile#L14
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "VITE_PADDLE_PW_AUTH") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/

Artifacts

Produced during runtime
Name Size Digest
synzen~MonitoRSS~HXKAJ5.dockerbuild
105 KB
sha256:a1668b505b0866ae132f03b5db4d71832a3d22a55ceb4ee27c489cd08bab997f