Fix: Align models.dev refresh guard with lookup#883
Merged
steipete merged 2 commits intosteipete:mainfrom May 10, 2026
Merged
Conversation
iam-brain
changed the title
steipete
force-pushed
the
iam-brain/models-dev-pinned-snapshot-guard
branch
from
cb3de5a to
38d706c
Compare
steipete
approved these changes
May 10, 2026
Owner
steipete
left a comment
steipete
left a comment
There was a problem hiding this comment.
Looks good. The continuity guard now uses the same pricing lookup path as runtime, with a pinned-snapshot regression test. Local focused test and make check passed; CI green.
This was referenced May 10, 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.
Summary
Follow-up to #881 / #863 for the pinned snapshot continuity edge case.
pricing(modelID:)lookup used at runtime@YYYYMMDDsnapshots as covering one another when no base/default candidate existsclaude-sonnet-4@20250101vsclaude-sonnet-4@20250201Verification