Repository navigation
chore(opencode): refresh Sol defaults to GPT-6.2 - #135
Merged
Merged
Conversation
Chart CI passedRepository hygiene and Helm validation passed. View the workflow run. |
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
Bump the OpenCode chart to 0.5.10. Update the global model, ten primaries, and five Sol reviewers to GPT-6.2 Sol. Preserve modes and reasoning variants, appVersion 2.0.22, API selector 2, and all other model pins. Astra and MiniMax are out of scope.
Type of change
Validation
Independent adversarial review found no Critical/High defects. CI is authoritative for hygiene, Helm rendering, exact model and historical parity assertions, and packaging. No inference or rollout verification yet.
Impact and rollout
Owner authorized merge after CI. Chart merge publishes the immutable OCI artifact and starts the existing generated GitOps pin PR. Couple that PR's pin with its exact chart/API assertion (0.5.10, 2). Keep both changes together and wait for consumer CI. Verify publication, consumer merge, Argo root and child revision and health, workload replacement, and fresh-session inference separately. Roll back via a reviewed GitOps pin and matching assertion reverting to 0.5.9; no manual sync or restart.
Safety and secrets
AI-assisted implementation and review.