Pin black version for consistent CI formatting #7304
Merged
+100
−5
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
- Add black==26.1.0 to dev dependencies - Update CI Lint job to use uv sync instead of external action - Ensures local and CI use same black version from uv.lock
MaxGhenis
added a commit
that referenced
this pull request
Jan 31, 2026
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
Pins black==26.1.0 in dev dependencies and updates CI to use uv sync for consistent formatting between local and CI environments.
Problem
Local developers may have different black versions installed than CI, causing lint failures even when code is properly formatted locally.
Solution
black==26.1.0to pyproject.toml dev dependenciesuv sync --extra devanduv run blackinstead of external actionTest plan
make formatuses correct black version🤖 Generated with Claude Code