build: Release chart/agh3 v3.5.0

[lkclab-agent-01]

User description

• Chart Version: 3.5.0
• App Version: 3.3.0
  • Captain: v1.5.1
  • Controller: v0.7.1
  • UI: v1.3.1
  • Report: v1.0.2

---

PR Type

enhancement, other

---

Description

• Bumped chart version to 3.5.0.
• Updated application version to v3.3.0.
• Updated Captain image tag to v1.5.1.
• Updated UI image tag to v1.3.1.

---

Changes walkthrough 📝

	Relevant files
Enhancement	Chart.yaml Bump chart and application versions.                                          charts/agh3/Chart.yaml Updated chart version to 3.5.0. Updated application version to v3.3.0. +2/-2      values.yaml Update Captain and UI image tags.                                                charts/agh3/values.yaml Updated Captain image tag to v1.5.1. Updated UI image tag to v1.3.1. +2/-2

---

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

[ai-themis]

PR Reviewer Guide 🔍

⏱️ Estimated effort to review [1-5]	1
🧪 Relevant tests	No
🔒 Security concerns	No
⚡ Key issues to review	None

[ai-themis]

PR Code Suggestions ✨

Category	Suggestion	Score
Best practice	Quote the version number to maintain consistency and avoid potential parsing issues Ensure that the version field is quoted to maintain consistency with the appVersion field and to avoid potential parsing issues. charts/agh3/Chart.yaml [16] -version: 3.5.0 +version: "3.5.0" Suggestion importance[1-10]: 8 Why: Quoting the version number is a good practice for consistency and to avoid potential parsing issues, especially in YAML files.	8
Maintainability	Use a variable for the image tag to simplify future updates Consider using a variable for the image tag to make it easier to manage and update in the future. charts/agh3/values.yaml [454] -tag: v1.5.1 +tag: {{ .Values.captain.image.tag }} Suggestion importance[1-10]: 7 Why: Using a variable for the image tag improves maintainability by simplifying future updates, though it is not crucial for functionality.	7
	Use a variable for the UI image tag to simplify future updates Consider using a variable for the UI image tag to make it easier to manage and update in the future. charts/agh3/values.yaml [564] -tag: v1.3.1 +tag: {{ .Values.ui.image.tag }} Suggestion importance[1-10]: 7 Why: Using a variable for the UI image tag enhances maintainability by making future updates easier, but it is not essential for the current functionality.	7