chore: refresh the dev toolchain - #97
Merged
Merged
Conversation
The lock had drifted a long way behind the fleet: ruff 0.15.17 against 0.16.8, ty 0.0.49 against 0.0.82. Floors move with it. ruff 0.16 formats Python inside markdown fences, which is why an archived plan doc reformats here; the rest of the fleet already lints under that behaviour. ruff check and ty check are both clean at the new versions.
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.
The specifiers here read
ruff>=0.15.16andty>=0.0.44, which looked merely permissive, but the lock had settled a long way back and that is what CI actually ran:rufftypytestFloors move with the lock so the gap cannot silently reopen.
One documentation file reformats:
ruff0.16 began formatting Python inside markdown fences, which takes this repo from 10 linted files to 22. The change is confined to blank lines between defs in an archived plan's code samples. pharos and sphragis have been linting under that behaviour for a while, so this brings phalanx-fl onto the same footing rather than introducing anything new.Verification
At the new versions, with the extras CI uses:
ruff check .— all checks passed.ty check— all checks passed (no suppressions added).ruff format .— 1 file reformatted, 21 unchanged.uv lock --check— consistent.uv run --extra hf --extra torch python -m pytest --cov=phalanx— 18 passed.