fix(product-console): release product-console 1.6.0#1243
fix(product-console): release product-console 1.6.0#1243ferr3ira-gabriel merged 9 commits intomainfrom
Conversation
Bump appVersion and image tag from 1.5.0 to 1.6.0 Image: ghcr.io/lerianstudio/product-console:1.6.0 Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
…le-1.6.0 chore(product-console): update to 1.6.0
Add artifacthub.io/images annotation to Chart.yaml to improve artifact traceability and trigger helm chart release. Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
…e-trigger fix(product-console): add image annotation for product-console 1.6.0
## (2026-04-17) ### Features * **plugin-fees:** add IAM Roles Anywhere sidecar support ([d9621a1](d9621a1)) * **plugin-fees:** add MULTI_TENANT_ALLOW_INSECURE_HTTP to configmap template ([48cf209](48cf209)) * **plugin-fees:** add multi-tenant support and fix AVP secret rendering ([#1229](#1229)) ([04e12ac](04e12ac)) ### Bug Fixes * **product-console:** add image annotation for product-console 1.6.0 ([03c927c](03c927c)) * **configmap:** add new configuration options for deployment mode, private upstreams, and reconciliation settings ([f1a475e](f1a475e)) * **plugin-fees:** remove MULTI_TENANT_SETTINGS_CHECK_INTERVAL_SEC from configmap ([f3e7f9b](f3e7f9b)) * **midaz:** update midaz-crm@3.6.2, midaz-ledger@3.6.2 ([960a392](960a392))
WalkthroughBumps Product Console chart version to 2.2.0-beta.2 and application version to 1.6.0, updating README mapping, Changes
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@charts/product-console/Chart.yaml`:
- Around line 36-39: The Artifact Hub image annotation in Chart.yaml
(annotations -> artifacthub.io/images) is inconsistent with the chart's deploy
default defined in values.yaml (image.repository) and used in
templates/deployment.yaml; update one of them so both point to the same
registry/repository and tag—either change the annotation entry for name/image to
match values.yaml (e.g., lerianstudio/product-console:1.6.0) or change
values.yaml.image.repository to include the ghcr.io registry
(ghcr.io/lerianstudio/product-console) so the image referenced by
templates/deployment.yaml and the Chart.yaml annotation are identical.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: a6625026-2c8c-4444-a778-8901c7953e37
📒 Files selected for processing (3)
README.mdcharts/product-console/Chart.yamlcharts/product-console/values.yaml
The artifacthub.io/images annotation referenced ghcr.io/lerianstudio/product-console while values.yaml uses lerianstudio/product-console (Docker Hub). Remove the annotation as it was only added to trigger a release. Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
…-annotation fix(product-console): remove inconsistent artifacthub image annotation
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@charts/product-console/Chart.yaml`:
- Line 20: The Chart.yaml currently sets a prerelease version "2.2.0-beta.1";
update the chart version field (version:) in Chart.yaml to the stable release
"1.6.0" so the chart is recognized as a stable release and aligns with the PR
objective promoting release 1.6.0 to main.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: 91cf3597-cbc9-447a-a58e-e1423ee04101
📒 Files selected for processing (1)
charts/product-console/Chart.yaml
| # This is the chart version. This version number should be incremented each time you make changes | ||
| # to the chart and its templates, including the app version. | ||
| version: 2.1.0 | ||
| version: 2.2.0-beta.1 |
There was a problem hiding this comment.
Use a stable chart version for this stable release.
2.2.0-beta.1 conflicts with the PR objective of promoting a stable 1.6.0 release to main. This may cause downstream consumers to treat this chart as prerelease-only.
Proposed fix
-version: 2.2.0-beta.1
+version: 2.2.0📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| version: 2.2.0-beta.1 | |
| version: 2.2.0 |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@charts/product-console/Chart.yaml` at line 20, The Chart.yaml currently sets
a prerelease version "2.2.0-beta.1"; update the chart version field (version:)
in Chart.yaml to the stable release "1.6.0" so the chart is recognized as a
stable release and aligns with the PR objective promoting release 1.6.0 to main.
There was a problem hiding this comment.
Actionable comments posted: 1
♻️ Duplicate comments (1)
charts/product-console/Chart.yaml (1)
20-20:⚠️ Potential issue | 🟠 MajorUse a stable chart version for
mainrelease publishing.
2.2.0-beta.2conflicts with the PR’s stable release objective and the repository release policy formain; this should be a stable semver (e.g.,2.2.0). This is the root cause for downstream mismatches such as the README mapping.Proposed fix
-version: 2.2.0-beta.2 +version: 2.2.0🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@charts/product-console/Chart.yaml` at line 20, The Chart.yaml currently sets an unstable pre-release version "version: 2.2.0-beta.2"; change this to a stable semver (for example "2.2.0") so the chart version matches the main branch release policy and downstream docs; update the `version` field in Chart.yaml (replace the "2.2.0-beta.2" token) and then reconcile any references (e.g., README mapping or other files that reference the chart version) to the new stable version.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@README.md`:
- Line 198: Update the README table row that currently reads `2.2.0-beta.2 |
1.6.0` so the left-hand version exactly matches the stabilized semver set in the
product-console Chart.yaml (replace `2.2.0-beta.2` with the new chart version
and keep the mapping consistent), and commit that README change in the same
commit where you change the Chart.yaml version.
---
Duplicate comments:
In `@charts/product-console/Chart.yaml`:
- Line 20: The Chart.yaml currently sets an unstable pre-release version
"version: 2.2.0-beta.2"; change this to a stable semver (for example "2.2.0") so
the chart version matches the main branch release policy and downstream docs;
update the `version` field in Chart.yaml (replace the "2.2.0-beta.2" token) and
then reconcile any references (e.g., README mapping or other files that
reference the chart version) to the new stable version.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: 4a6705cb-0708-4d4d-8f2c-d5fb4cef3418
📒 Files selected for processing (2)
README.mdcharts/product-console/Chart.yaml
| | Chart Version | Console Version | | ||
| | :---: | :---: | | ||
| | `2.1.0` | 1.5.0 | | ||
| | `2.2.0-beta.2` | 1.6.0 | |
There was a problem hiding this comment.
Keep this mapping synchronized with the chart version fix.
Once charts/product-console/Chart.yaml Line 20 is changed to stable semver, update this row to match in the same commit.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@README.md` at line 198, Update the README table row that currently reads
`2.2.0-beta.2 | 1.6.0` so the left-hand version exactly matches the stabilized
semver set in the product-console Chart.yaml (replace `2.2.0-beta.2` with the
new chart version and keep the mapping consistent), and commit that README
change in the same commit where you change the Chart.yaml version.
gandalf-at-lerian
left a comment
gandalf-at-lerian
left a comment
There was a problem hiding this comment.
Straightforward version bump — 1.5.0 → 1.6.0 for product-console, image tag and appVersion aligned. CI green. LGTM.
One thing CodeRabbit flagged three times and I agree with: chart version 2.2.0-beta.2 going to main. If this is a stable release promotion (which the PR description says — "promote from develop to main for stable release"), shouldn't the chart version be 2.2.0 (no beta suffix)? Pre-release semver on main is unusual unless there's a specific reason.
Not blocking — you know the release conventions better than I do. But worth a second look before merge.
4 participants
Changes
Promote product-console updates from develop to main for stable release.
Product Console
appVersionfrom1.5.0to1.6.0image.tagfrom1.5.0to1.6.0artifacthub.io/imagesannotation for artifact traceabilityImage:
ghcr.io/lerianstudio/product-console:1.6.0