Update to new Evolution API image source and pin it to the latest version

[matheusfelipeog]

The Evolution API Docker image is no longer located at atendai/evolution-api. It is now located at evoapicloud/evolution-api.

The currently pinned version is v2.1.2. This version does not work correctly and contains vulnerabilities that have already been fixed in more recent versions.

I updated the image to the new source and pinned the version to latest.

closes #428 #430

related:

• correct evolution api docker image to the latest one and implement missing configuration for the latest features  #429
• feat: Add Evo AI blueprint and enhance Evolution API configuration #540

[github-actions]

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name	Status	Preview	Last Commit
templates	✅ Ready (View Log)	Visit Preview	e127cb1

[Copilot]

Pull request overview

This PR updates the Evolution API Docker image source from the deprecated atendai/evolution-api to the new official location evoapicloud/evolution-api. The change addresses issues #428 and #430, where the old v2.1.2 version contained vulnerabilities and didn't work correctly.

Key Changes:

• Updates Docker image source from atendai/evolution-api:v2.1.2 to evoapicloud/evolution-api:latest

[Copilot]

Using the latest tag violates project conventions. According to the project guidelines, images must be pinned to specific versions in docker-compose.yml. The latest tag should never be used as it can break templates when upstream images change unexpectedly.

Please update this to a specific version tag (e.g., evoapicloud/evolution-api:v2.2.0 or whatever the current stable version is). You should verify the image exists using docker manifest inspect evoapicloud/evolution-api:<version> before committing.

[matheusfelipeog]

Just a comment on this:

I don’t agree with pinning a fixed version for the Evolution API template, because features frequently stop working correctly due to updates in projects that Evolution API depends on (WhatsApp, Baileys, etc). That would mean we would constantly need to update the template version here so others don’t end up using something broken, vulnerable, or outdated. Not to mention the creation of issues assuming it’s a Dokploy problem, when in fact it’s caused by the pinned version.

By pinning the version to latest, we ensure that a functional and theoretically secure version is being used by users.