chore: preserve Ruff lint policy while updating dev range - #103
Merged
Merged
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
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.
Ruff 0.16 changed its default rule set, so widening the dev dependency alone produces hundreds of new diagnostics while also dropping 18 previously enabled checks. Make AgentCheck's existing
E4,E7,E9, andFpolicy explicit and permit Ruff versions below 0.17.Verified that Ruff 0.12.12's existing defaults and Ruff 0.16.6 with this configuration enable the same 59 rules. Both pass the current source tree; six positive/negative controls on each version retain exact expected diagnostics, including checks removed from Ruff's new defaults. Tool binaries were bound to pinned public wheels. Independent review covers policy preservation and potentially substantive newly exposed diagnostics.
Supersedes the ceiling-only proposal in #87. Development configuration only; package version and runtime behavior are unchanged, so no release is planned for this change.