Repository navigation
fix(ai): stabilize cache retention CI fixtures - #286
Merged
Merged
Conversation
- Exercise generated compatibility flags with stable upstream inputs - Preserve request assertions when the live model catalog renames entries
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
Fix main CI after the upstream OpenCode catalog renamed
deepseek-v4-flash.Reasoning
Compatibility request tests should remain stable when upstream catalog entries disappear or change names.
Using the existing offline generator fixture preserves coverage of the production compatibility overrides and outgoing request payloads.
Changes
Testing
./test.sh other --shard=2/2passes with isolated credentials.npm run checkpasses.