Fix ruff F601: duplicate release-date keys from the refreeze - #158
Merged
Conversation
The refreeze already carried both entries; a second pair landed while working around a PYTHONPATH issue in the local render. Values were identical, so nothing rendered differently — only ruff F601 failed. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
1 participant
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.
Removes the duplicate
grok-4.6/ox-alphaentries inMODEL_RELEASE_DATES(identical values; the refreeze already carried them). This repairs the lint failure on main that #157 merged with — that merge slipped through a broken pre-merge guard on my side, documented in the PR comment below.🤖 Generated with Claude Code