Uh oh!
There was an error while loading. Please reload this page.
chore(release): bump chart to 1.9.10 after the v1.9.9 release - #536
Merged
Conversation
v1.9.9 shipped to main on 2026-08-03 (tag + GitHub Release + Helm chart published). Chart.yaml still said 1.9.9, so the next develop -> staging hop would have refused with 'v1.9.9 already exists' before merging anything. version and appVersion move together, as they have for every release in this repo. The train reads Chart.yaml as the DECLARED NEXT release and never writes it, so every release leaves the file equal to what just shipped. Patch bump is a floor, not a judgement about what comes next. Refs: tracebloc/backend#1405
saadqbal
approved these changes
Aug 3, 2026
Uh oh!
There was an error while loading. Please reload this page.
LukasWodka
commented
Aug 3, 2026
ContributorAuthor
/fr-pass |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
v1.9.9shipped tomainthis morning — tag, GitHub Release, and the Helm chart published to the public index.client/Chart.yamlstill said1.9.9, so the nextdevelop → staginghop would have refused before merging anything:Same refusal
data-ingestors,design-systemandtracebloc-py-packagehit in today's prod hop. Correct behaviour — the train will not mint a duplicate tag — but avoidable here.For this repo it matters more than most: a Helm repo only ever publishes a new version, so an unbumped chart edit either reaches no install at all or silently overwrites an already-published one. Both have happened here (
#472's dark ship;ingestor-0.2.0.tgzoverwritten 5×).Scope
versionandappVersionmove together, as they have for every release in this repo. No chart content touched, sochart-version-guardreports N/A.1.9.10is a floor, not a judgement about what comes next — raise it to1.10.0if the next release carries features.Refs: tracebloc/backend#1405
🤖 Generated with Claude Code
Note
Low Risk
Metadata-only version bump with no chart logic or deployment behavior changes.
Overview
Bumps
client/Chart.yamlversionandappVersionfrom 1.9.9 to 1.9.10 so the next release train can tag and publish without colliding with the shipped v1.9.9 chart. No templates, values, or other chart content changes.Reviewed by Cursor Bugbot for commit e9d379c. Bugbot is set up for automated code reviews on this repo. Configure here.