Skip to content

fix(evolution): prevent Evolution instances from getting stuck in 'cl… #380

fix(evolution): prevent Evolution instances from getting stuck in 'cl…

fix(evolution): prevent Evolution instances from getting stuck in 'cl… #380

Triggered via push May 17, 2026 22:23
Status Success
Total duration 8m 58s
Artifacts 1
Build and Deploy
8m 55s
Build and Deploy
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
Build and Deploy
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@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. 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: Dockerfile#L42
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "LICENSE_ENDPOINT_XOR_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: Dockerfile#L40
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "LICENSE_ENDPOINT_XOR_KEY") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/

Artifacts

Produced during runtime
Name Size Digest
evolution-foundation~evolution-api~O1DI95.dockerbuild
153 KB
sha256:d5948a3de6a6bdc365309fafa6d5a2291b9543d8920d8efeefaf8d9f993aca63