Update Helm chart

[Pinchez25]

What is the Purpose?

What was the approach?

How can the changes made get tested?

Are there any concerns to addressed further before or after merging this PR?

Mentions?

Issue(s) affected?

[willymwai]

/improve

[willymwai]

/describe

[willymwai]

/review

[willymwai]

/improve

[willymwai]

/review

[qodo-code-review]

PR Code Suggestions ✨

Category	Suggestion	Impact
General	Consider major version bump The version bump from 0.3.35 to 0.4.0 indicates a minor version change, but the appVersion changed from 1.17.35 to 1.18.0. Consider whether this should be a major version bump (1.0.0) if there are breaking changes in the application. charts/jisort/Chart.yaml [19] -version: 0.4.0 +version: 1.0.0 Apply / Chat Suggestion importance[1-10]: 5 __ Why: The suggestion raises a valid point about semantic versioning alignment between the chart and the application, but the author's choice of a minor version bump is also a reasonable strategy.	Low
More

[qodo-code-review]

PR Code Suggestions ✨

Category	Suggestion	Impact
General	Consider major version bump The version bump from 0.3.35 to 0.4.0 indicates a minor version change, but the appVersion changed from 1.17.35 to 1.18.0. Consider whether this should be a major version bump (1.0.0) if there are breaking changes in the application. charts/jisort/Chart.yaml [19] -version: 0.4.0 +version: 1.0.0 Apply / Chat Suggestion importance[1-10]: 5 __ Why: The suggestion raises a valid point about semantic versioning alignment between the chart and the application, but the author's choice of a minor version bump is also a reasonable strategy.	Low
More

[qodo-code-review]

PR Reviewer Guide 🔍

(Review updated until commit 522104c)

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Version Mismatch The chart version was bumped from 0.3.35 to 0.4.0 (major version bump) while appVersion changed from 1.17.35 to 1.18.0. Need to verify if this major version bump is intentional and follows the project's versioning strategy. version: 0.4.0 # This is the version number of the application being deployed. This version number should be # incremented each time you make changes to the application. Versions are not expected to # follow Semantic Versioning. They should reflect the version the application is using. # It is recommended to use it with quotes. appVersion: "1.18.0" Image Tag Format Docker image tags are using short commit hashes (63ee17, 56e5e8) instead of semantic versions. This makes it difficult to track what version is being deployed and may cause issues with rollbacks or version management. tag: 63ee17 resources: limits: {} requests: {} ## Client resource requests and limits client: resources: limits: {} requests: {} image: name: truehostcloud/mifos-web-app tag: 56e5e8

[qodo-code-review]

Title

(Describe updated until commit 522104c)

Update Helm chart

---

User description

What is the Purpose?

What was the approach?

How can the changes made get tested?

Are there any concerns to addressed further before or after merging this PR?

Mentions?

Issue(s) affected?

---

PR Type

Enhancement

---

Description

• Update Helm chart version from 0.3.35 to 0.4.0

• Bump application version from 1.17.35 to 1.18.0

• Update Docker image tags for server and client components

---

Changes diagram

flowchart LR
  A["Chart 0.3.35"] --> B["Chart 0.4.0"]
  C["App 1.17.35"] --> D["App 1.18.0"]
  E["Server tag e4bc76"] --> F["Server tag 63ee17"]
  G["Client tag 64581d"] --> H["Client tag 56e5e8"]

Loading

---

Changes walkthrough 📝

	Relevant files
Enhancement	Chart.yaml Bump chart and application versions                                            charts/jisort/Chart.yaml Increment chart version from 0.3.35 to 0.4.0 Update appVersion from 1.17.35 to 1.18.0 +2/-2
Configuration changes	values.yaml Update Docker image tags                                                                  charts/jisort/values.yaml Update server image tag from e4bc76 to 63ee17 Update client image tag from 64581d to 56e5e8 +2/-2

---

Need help?

Type /help how to ... in the comments thread for any questions about Qodo Merge usage.

Check out the documentation for more information.

[qodo-code-review]

Persistent review updated to latest commit f0ba003

[willymwai]

The versioning is likely wrong.

MAJOR.MINOR.PATCH

MAJOR version when you make incompatible API changes
MINOR version when you add functionality in a backward compatible manner
PATCH version when you make backward compatible bug fixes

[willymwai]

/review

[willymwai]

/improve

[willymwai]

/describe

[willymwai]

/review

[willymwai]

/improve

[qodo-code-review]

PR Code Suggestions ✨

Category	Suggestion	Impact
General	Consider major version bump The version bump from 0.3.35 to 0.4.0 indicates a minor version change, but the appVersion changed from 1.17.35 to 1.18.0. Consider whether this should be a major version bump (1.0.0) if there are breaking changes in the application. charts/jisort/Chart.yaml [19] -version: 0.4.0 +version: 1.0.0 Apply / Chat Suggestion importance[1-10]: 5 __ Why: The suggestion raises a valid point about semantic versioning alignment between the chart and the application, but the author's choice of a minor version bump is also a reasonable strategy.	Low
More

[qodo-code-review]

Persistent review updated to latest commit 522104c

[qodo-code-review]

Persistent review updated to latest commit 522104c

[qodo-code-review]

PR Code Suggestions ✨

Category	Suggestion	Impact
General	Consider major version bump The version bump from 0.3.35 to 0.4.0 indicates a minor version change, but the appVersion changed from 1.17.35 to 1.18.0. Consider whether this should be a major version bump (1.0.0) if there are breaking changes in the application. charts/jisort/Chart.yaml [19] -version: 0.4.0 +version: 1.0.0 Apply / Chat Suggestion importance[1-10]: 5 __ Why: The suggestion raises a valid point about semantic versioning alignment between the chart and the application, but the author's choice of a minor version bump is also a reasonable strategy.	Low
More