Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
matheusfelipeog wants to merge 1 commit into
base: canary
Choose a base branch
from
Open

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

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion blueprints/evolutionapi/docker-compose.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
services:
evolution-api:
image: atendai/evolution-api:v2.1.2
image: evoapicloud/evolution-api:latest
Copy link

Copilot AI Jan 8, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copilot generated this review using guidance from repository custom instructions.
Copy link
Author

@matheusfelipeog matheusfelipeog Jan 8, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

restart: always
volumes:
- evolution-instances:/evolution/instances
Expand Down
Loading