Skip to content

chore(chart): bump to 1.9.113 so #1033's template change publishes (version collided with #1032) - #1040

Merged
LukasWodka merged 1 commit into
developfrom
chore/bump-chart-1.9.113
Sep 10, 2026
Merged

chore(chart): bump to 1.9.113 so #1033's template change publishes (version collided with #1032)#1040
LukasWodka merged 1 commit into
developfrom
chore/bump-chart-1.9.113

Conversation

@LukasWodka

@LukasWodka LukasWodka commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

Summary

Chart version bump only: client/Chart.yaml 1.9.112 → 1.9.113 (version + appVersion). No template, values or script change.

Why

#1033 (image-refresh: gate the fresh-install re-pin roll on a digest-applied marker) bumped the chart 1.9.111 → 1.9.112 on its branch, and #1032 (control-plane trim) did the same. Both merged to develop; the second bump was a no-op. The chart on develop now carries #1033's template change at the same version staging already has (1.9.112, released to prod as v1.9.112 at 17:51 UTC), so the required chart content ⇒ Chart.yaml version bump check refuses the develop→staging promotion (#1037). A Helm index publishes one package per version, so the guard is right to refuse.

Test plan

  • helm unittest 729/729 locally
  • chart-version-guard.bats green locally
  • After merge: recut the client staging mirror (recut_repos=client); the guard on the recut mirror must pass with 1.9.113 > 1.9.112

Checklist


Note

Low Risk
Version metadata only in Chart.yaml; no runtime or deployment logic changes in this diff.

Overview
Bumps the client Helm chart from 1.9.112 to 1.9.113 by updating both version and appVersion in Chart.yaml. There are no template, values, or script changes in this PR.

This republishes chart content that already landed on develop (including #1033’s image-refresh template work) under a new chart version, because #1032 and #1033 both advanced the chart to 1.9.112 and staging/prod already ship that version—so a content change without a higher version blocks develop→staging promotion and Helm index publishing.

Reviewed by Cursor Bugbot for commit cd42945. Bugbot is set up for automated code reviews on this repo. Configure here.

… same 1.9.112 that #1032 already shipped

The image-refresh CronJob fix (#1033) bumped Chart.yaml 1.9.111 -> 1.9.112 on its own
branch, and so did the control-plane trim (#1032). Both merged; the second bump was a
no-op, so develop's chart version now equals staging's while the templates differ, and
the chart-version guard rightly refuses the staging promotion. This bump carries #1033
to 1.9.113. No template change.
@LukasWodka LukasWodka self-assigned this Sep 10, 2026
@LukasWodka

Copy link
Copy Markdown
Contributor Author

bugbot run

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

Reviewed by Cursor Bugbot for commit cd42945. Configure here.

@saqlainsyed007 saqlainsyed007 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Clean version-only bump. Chart.yaml version and appVersion both go 1.9.112 → 1.9.113, a monotonic increase over the version currently on develop/staging/prod. Diff touches nothing but the two version lines — no template, values, or script changes ride along. This correctly re-publishes #1033's already-merged template content at a fresh chart version so the develop→staging promotion guard (one Helm package per version) can pass. CI green, Bugbot clean. Approving.

@LukasWodka
LukasWodka merged commit 186c494 into develop Sep 10, 2026
48 of 51 checks passed
@LukasWodka
LukasWodka deleted the chore/bump-chart-1.9.113 branch September 10, 2026 19:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants