Skip to content

chore(plugin-fees): bump fees version to 3.0.3#835

Merged
guimoreirar merged 4 commits intomainfrom
develop
Dec 4, 2025
Merged

chore(plugin-fees): bump fees version to 3.0.3#835
guimoreirar merged 4 commits intomainfrom
develop

Conversation

@guimoreirar
Copy link
Copy Markdown
Member

@guimoreirar guimoreirar commented Dec 4, 2025

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 Plugin Fees Helm Chart to version 3.4.5-beta.1 with application version 3.0.3.
  • Documentation

    • Updated version mapping documentation to reflect new releases.

✏️ Tip: You can customize this high-level summary in your review settings.

guimoreirar and others added 4 commits December 4, 2025 17:45
@guimoreirar guimoreirar requested a review from a team as a code owner December 4, 2025 20:58
@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Dec 4, 2025

Walkthrough

This PR updates the Plugin Fees Helm chart version and application version across three files. The chart version is bumped from 3.4.4 to 3.4.5-beta.1, the application version from 3.0.2 to 3.0.3, and the Docker image tag from 3.0.2 to 3.0.3. These changes are reflected in Chart.yaml, values.yaml, and README.md.

Possibly related PRs

Suggested labels

doc, plugin-fees

Suggested reviewers

  • ferr3ira-gabriel

Pre-merge checks and finishing touches

❌ Failed checks (1 warning, 1 inconclusive)
Check name Status Explanation Resolution
Description check ⚠️ Warning The PR description uses the required template but has incomplete and contradictory checklist responses. Check the appropriate PR Type boxes (currently both Plugin Fees and Documentation are checked, which may be unintended). Verify all development checklist items: documentation updates appear incomplete, and ensure the PR is targeted to develop branch as noted in observations.
Title check ❓ Inconclusive The title 'Develop' is too generic and vague; it does not clearly convey the specific changes (version updates to Plugin Fees chart) in the pull request. Provide a more descriptive title that summarizes the main change, such as 'Bump Plugin Fees chart version to 3.4.5-beta.1 and app version to 3.0.3'.
✅ Passed checks (1 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
  • 📝 Generate docstrings
🧪 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.

@linearb linearb bot added the 1 min review label Dec 4, 2025
@guimoreirar guimoreirar changed the title Develop chore(plugin-fees): bump fees version to 3.0.3 Dec 4, 2025
Copy link
Copy Markdown

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 2

🧹 Nitpick comments (1)
README.md (1)

55-60: Add blank lines around the version mapping table for markdown compliance.

Per markdown linting, tables should be surrounded by blank lines. The Plugin Fees version mapping table is missing spacing before (after line 54) and after (before line 60).

Apply this diff to add blank lines:

 🛠️ Looking for implementation and configuration details? See the [README](https://charts.lerian.studio/charts/plugin-fees).

 #### Application Version Mapping
+
 | Chart Version | Fees Version | UI Version |
 | :---: | :---: | :---: |
 | `3.4.5` | `3.0.3` | `3.0.0` |
+
 -----------------
📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a79b89f and 53fc9b8.

📒 Files selected for processing (3)
  • README.md (1 hunks)
  • charts/plugin-fees/Chart.yaml (1 hunks)
  • charts/plugin-fees/values.yaml (1 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.18.1)
README.md

59-59: Tables should be surrounded by blank lines

(MD058, blanks-around-tables)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (8)
  • GitHub Check: gitStream.cm
  • GitHub Check: gitStream.cm
  • GitHub Check: gitStream.cm
  • GitHub Check: gitStream.cm
  • GitHub Check: gitStream.cm
  • GitHub Check: gitStream.cm
  • GitHub Check: gitStream.cm
  • GitHub Check: gitStream.cm
🔇 Additional comments (2)
charts/plugin-fees/values.yaml (1)

19-19: Image tag update is consistent with appVersion.

The fees service image tag is correctly updated to 3.0.3, aligning with the appVersion change in Chart.yaml. The frontend image remains at 3.0.0, which appears intentional.

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

16-16: No version discrepancy found.

The Chart.yaml version is 3.4.5-beta.1. The README.md does not document or reference a chart version as 3.4.5 at line 59 or elsewhere. Line 59 contains ingress configuration, not version information. No inconsistency exists between the chart version and README documentation.

Likely an incorrect or invalid review comment.

Comment thread charts/plugin-fees/Chart.yaml
Comment thread README.md
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants