Repository navigation
chore(deps-dev): update Ruff and Hypothesis against current main - #50
Merged
Merged
Conversation
This was referenced Nov 15, 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
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.
Scope
Refresh the two existing development-tool updates from Dependabot PRs #47 and #48 against the latest
mainbranch. The original PRs were behind protected main, so GitHub correctly required a newhuman-authorship-policycheck on the current merge candidate.0.17.3→0.17.46.170.14→6.170.15Only
pyproject.tomlchanges, preserving all other application dependencies. This combined PR supersedes #47 and #48 if it passes and merges.Verification
Both original PRs previously passed Human authorship policy, CodeQL and Hardened CI, including tests. Those runs do not verify this new branch. Run the full required CI and current protected-branch checks for this PR before merge. No release or deployment is requested.
Changes were prepared using repository-connected automation at the repository owner's direction.