chore(helm): point the chart at app release 0.10.0 - #315
Merged
Merged
Conversation
A tagged release is not installable until the chart names it. v0.10.0 built release/backend-service:0.10.0 and release/frontend-service:0.10.0, and the chart still asked for 0.9.1 — so nothing a cluster could install carried the permission repair that release exists for. The chart's own version moves with it, because that is what decides whether a new chart gets published at all.
cmdoret
approved these changes
Sep 22, 2026
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 free
to 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.
Organisers on prod get the fix that's been sitting in main
An organiser could not open Manage Teams on the production deployment — the page failed with an unexplained error, while a platform administrator could open it fine. The repair for that has been on main and it has been decided to make a release.