Skip to content

fix: change service image version and change to latest config session phone version #1513

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.

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

Merged
merged 2 commits into from
May 28, 2025

Conversation

samuelterra22
Copy link
Contributor

@samuelterra22 samuelterra22 commented May 28, 2025

This pull request includes updates to configuration files to ensure compatibility with newer versions of dependencies and improve system functionality. The changes primarily involve updating version numbers for the Evolution API and the WhatsApp Web session configuration.

Updates to versioning:

  • .env.example: Updated CONFIG_SESSION_PHONE_VERSION to 2.3000.1023204200 to align with the latest WhatsApp Web version.
  • Docker/swarm/evolution_api_v2.yaml: Updated the Evolution API image version from v2.1.2 to v2.2.3 for improved functionality and compatibility.

Synchronization across configuration files:

  • Docker/swarm/evolution_api_v2.yaml: Updated CONFIG_SESSION_PHONE_VERSION to match the change in .env.example, ensuring consistency across configuration files.… phone version

Summary by Sourcery

Bump the Evolution API service image and align the WhatsApp Web session phone version config to the latest releases for improved compatibility.

Deployment:

  • Update Evolution API Docker image from v2.1.2 to v2.2.3
  • Synchronize CONFIG_SESSION_PHONE_VERSION to 2.3000.1023204200 across configuration files

Copy link
Contributor

sourcery-ai bot commented May 28, 2025

Reviewer's Guide

Updates the Evolution API Docker image to v2.2.3 and aligns CONFIG_SESSION_PHONE_VERSION across .env.example and swarm YAML to ensure compatibility with the latest WhatsApp Web session protocol.

File-Level Changes

Change Details Files
Bump Evolution API Docker image to v2.2.3
  • Updated service image tag from atendai/evolution-api:v2.1.2 to v2.2.3
Docker/swarm/evolution_api_v2.yaml
Synchronize CONFIG_SESSION_PHONE_VERSION across configs
  • Updated CONFIG_SESSION_PHONE_VERSION in .env.example to 2.3000.1023204200
  • Updated CONFIG_SESSION_PHONE_VERSION in swarm YAML to 2.3000.1023204200
.env.example
Docker/swarm/evolution_api_v2.yaml

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link
Contributor

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

Hey @samuelterra22 - I've reviewed your changes and they look great!

Here's what I looked at during the review
  • 🟡 General issues: 1 issue found
  • 🟢 Security: all looks good
  • 🟢 Testing: all looks good
  • 🟢 Documentation: all looks good

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@@ -2,7 +2,7 @@ version: "3.7"

services:
evolution_v2:
image: atendai/evolution-api:v2.1.2
image: atendai/evolution-api:v2.2.3
Copy link
Contributor

Choose a reason for hiding this comment

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

suggestion (bug_risk): Pin Docker image to a digest for immutability

Pinning to a digest ensures the deployed image won't change unexpectedly if the tag is updated.

Suggested implementation:

    image: atendai/evolution-api@sha256:abc123replacewithactualdigest

You must replace sha256:abc123replacewithactualdigest with the actual digest for atendai/evolution-api:v2.2.3. You can find this by running:

docker pull atendai/evolution-api:v2.2.3
docker inspect --format='{{index .RepoDigests 0}}' atendai/evolution-api:v2.2.3

and copying the sha256 value.

@samuelterra22
Copy link
Contributor Author

related issues: #1511 and #1512

@iaurg
Copy link

iaurg commented May 28, 2025

@samuelterra22 Have you considered updating to version 2.3000.1023243284? It’s the most recent version listed here, works well, and is likely to stay compatible for longer.

@samuelterra22
Copy link
Contributor Author

Hi @iaurg, on the website you suggested it seems to be all alpha versions. I extracted the version from the current version of Whatssapp Web but it can be modified without any problem.

@iaurg
Copy link

iaurg commented May 28, 2025

Hi @iaurg, on the website you suggested it seems to be all alpha versions. I extracted the version from the current version of Whatssapp Web but it can be modified without any problem.

Interesting—I’ve checked several sources, but they all seem a bit confusing:
• Here, I’m following the official environment variable example from Evolution API and the atendeai/evolution Docker image (.env.example). This endpoint: https://web.whatsapp.com/check-update?version=0&platform=web (but its format is different).
• The OrionDesign setup (code), but it doesn’t actually show the version. Also checked: https://web.whatsapp.com/sw.js
• The latest commit on Baileys, made just yesterday: commit link.
• And, finally, by opening WhatsApp Web > Help > Version:
image

Where did you find the version you shared? Maybe we could define a single “source of truth” for future updates.

@DavidsonGomes DavidsonGomes changed the base branch from main to develop May 28, 2025 14:00
@DavidsonGomes DavidsonGomes merged commit a53e0a8 into EvolutionAPI:develop May 28, 2025
1 check passed
@samuelterra22 samuelterra22 deleted the patch-1 branch May 28, 2025 17:03
Copy link

@Phristyle Phristyle left a comment

Choose a reason for hiding this comment

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

meu erro permanece

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants