Repository navigation
chore(opencode): bump chart to 0.5.4 - #286
Merged
Merged
Conversation
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
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.
Summary
Select published opencode-server chart 0.5.4 from charts PR #129, and coordinate the existing exact chart/API assertion to (0.5.4, 2). Exporter API selector remains 2. No test relaxation, workflow behavior, image, Secret, RBAC, network or pilot changes.
Validation
07cfd08613e64ce2505c3afa96e6d7913d970908. No local checks claimed.Impact and rollout
Owner authorized proceeding with consumer coordination. Existing generated PR auto-merge is enabled and check-gated. A merge runs main CI; successful main automatically requests root sync at the tested SHA, then gitops-workloads updates the opencode child. Root/child revision reconciliation, resource/pod health, delivered configuration and runtime behavior remain separately verified; no manual sync or live patch is performed. Recreate rollout may briefly interrupt the single-replica server. Image/appVersion 2.0.22 unchanged. Stored/client-selected sessions retain model precedence; new model entitlement, effective effort, inference/tool-call success and comparative quality/cost are not established by static CI.
Rollback requires a reviewed GitOps pin and matching exact assertion to a published prior version; no retagging, image downgrade or database operation.
Safety
No plaintext secrets, decrypted values, credentials, state or kubeconfigs retrieved or changed. AI-assisted scoped follow-up; generated chart pin remains publisher-owned.