chore(midaz): bump app version to 3.4.1

[guimoreirar]

Midaz Pull Request Checklist

Pull Request Type

• Midaz
• Plugin Access Manager
• Plugin CRM
• Reporter
• Plugin Fees
• Plugin BR PIX Direct JD
• Otel Collector
• Pipeline
• Documentation

Checklist

Please check each item after it's completed.

• I have tested these changes locally.
• I have updated the documentation accordingly.
• I have added necessary comments to the code, especially in complex areas.
• I have ensured that my changes adhere to the project's coding standards.
• I have checked for any potential security issues.
• I have ensured that all tests pass.
• I have updated the version appropriately (if applicable).
• I have confirmed this code is ready for review.

Additional Notes

Obs: Please, always remember to target your PR to develop branch instead of main.

Summary by CodeRabbit

• Chores
  • Updated Helm chart versions and application component versions across multiple charts (Midaz, Plugin BR PIX Direct JD, Plugin Fees, and Reporter).
  • Image tags updated to reflect latest application release versions.

[coderabbitai]

Walkthrough

This pull request bumps version numbers across multiple Helm charts. The Midaz Helm chart is updated with a new chart version (4.4.0-beta.11) and application version (3.4.1), along with corresponding image tag updates for console, onboarding, and transaction components. The README's Application Version Mapping table is updated to reflect these changes. Additionally, chart versions are bumped for plugin-br-pix-direct-jd (to 1.2.1-beta.1), plugin-fees (to 3.4.1-beta.1), and reporter (to 1.1.1-beta.1).

Possibly related PRs

• chore(midaz): bump app version to 3.4.1 #756: Makes identical code-level changes to the Midaz chart, bumping appVersion and image tags from 3.4.0 to 3.4.1
• feat(midaz): add transaction gRPC configuration and update service versions #742: Modifies charts/midaz Helm metadata and values in Chart.yaml and values.yaml
• chore(midaz): update component versions in README file #745: Updates Midaz version references across README Application Version Mapping and midaz chart appVersion entries

Suggested reviewers

• ferr3ira-gabriel

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly describes the main change: bumping the application version to 3.4.1 across Midaz components.
Description check	✅ Passed	The description follows the template structure with PR type and checklist sections completed, though some checklist items were not checked despite version updates occurring.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch develop

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[guimoreirar]

@coderabbitai help

[coderabbitai]

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

CodeRabbit commands

These commands are invoked using PR/Issue comments.

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai evaluate custom pre-merge check --instructions <custom-checks-instructions> --name <custom-checks-title> [--mode <error|warning>] to validate the custom pre-merge checks instructions. Defaults to error when --mode is omitted.
  • @coderabbitai ignore pre-merge checks to override pre-merge checks and get an approval on PR.
  • @coderabbitai run pre-merge checks to run pre-merge checks on the pull request.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve to resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore or @coderabbit ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit configuration file (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• You can also validate your configuration using the online YAML validator.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, support, documentation and community

• Visit our status page to check the current availability of CodeRabbit.
• Create a ticket on our support page for assistance with any issues or questions.
• Visit our documentation site for detailed information on how to use CodeRabbit.
• Join our Discord community to connect with other users and get help from the community.
• Follow us on X/Twitter for updates and announcements.

[guimoreirar]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[coderabbitai]

Actionable comments posted: 2

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6ebb41b and 2aceb38.

📒 Files selected for processing (6)

• README.md (1 hunks)
• charts/midaz/Chart.yaml (1 hunks)
• charts/midaz/values.yaml (3 hunks)
• charts/plugin-br-pix-direct-jd/Chart.yaml (1 hunks)
• charts/plugin-fees/Chart.yaml (1 hunks)
• charts/reporter/Chart.yaml (1 hunks)

🧰 Additional context used

🪛 markdownlint-cli2 (0.18.1)

README.md

19-19: Tables should be surrounded by blank lines

(MD058, blanks-around-tables)

🔇 Additional comments (5)

charts/reporter/Chart.yaml (1)

19-19: Version bump is clean and consistent.

The chart version bump from 1.1.0 to 1.1.1-beta.1 follows semantic versioning, with appVersion appropriately left unchanged at 3.1.0.

charts/midaz/values.yaml (1)

46-46: Image tags consistently bumped to match appVersion.

All three component image tags (console, onboarding, transaction) are updated from 3.4.0 to 3.4.1, aligning with the appVersion bump in charts/midaz/Chart.yaml.

Also applies to: 240-240, 440-440

charts/plugin-br-pix-direct-jd/Chart.yaml (1)

15-15: Version bump is correct and consistent.

Chart version bumped from 1.2.0 to 1.2.1-beta.1, with appVersion appropriately unchanged at 1.0.0.

charts/plugin-fees/Chart.yaml (1)

16-16: Version bump is correct and consistent.

Chart version bumped from 3.4.0 to 3.4.1-beta.1, with appVersion appropriately unchanged at 2.1.1.

charts/midaz/Chart.yaml (1)

20-23: Verify versioning scheme and update README.md to match chart version.

The chart version in Chart.yaml is 4.4.0-beta.11 (beta), but README.md documents the installation command with --version 4.4.0 (release). These must match. Additionally, clarify the versioning approach:

1. Should the chart version be 4.4.0 or 4.4.0-beta.11?
2. Why is the chart version using a beta designation after a release version (reverses typical semantic versioning order)—is this intentional?
3. Update README.md to reflect the actual chart version in Chart.yaml.

The appVersion bump to 3.4.1 is correct and aligns with the image tags in charts/midaz/values.yaml.