Skip to content

chore(deps): update dependency ruff to v0.16.2 - #245

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/ruff-0.x
Open

chore(deps): update dependency ruff to v0.16.2#245
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/ruff-0.x

Conversation

@renovate

@renovate renovate Bot commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
ruff (source, changelog) ==0.15.22==0.16.2 age adoption passing confidence

Release Notes

astral-sh/ruff (ruff)

v0.16.2

Compare Source

Released on 2026-08-06.

Bug fixes
  • [flake8-pyi] Avoid false positives on singledispatch functions (PYI041) (#​27335)
Server
  • Register formatting capabilities dynamically to exclude TOML files (#​27332)
Contributors

v0.16.1

Compare Source

Released on 2026-07-30.

Preview features
  • Add an option to opt out of human-readable names (#​27160)
  • [flake8-pytest-style] Make fixes safe by default and unsafe only when comments are present (PT018) (#​27201)
  • [pyupgrade] Skip fix when a defaulted TypeVar precedes a non-defaulted one (UP040, UP046, UP047) (#​27133)
  • [ruff] Fix false positive with unpacked arguments (RUF065) (#​26959)
Bug fixes
  • Bump gen-lsp-types to gracefully handle unknown enumeration values in LSP messages (#​27230)
  • [flake8-bugbear] Mark range as immutable (B008) (#​27247)
  • [flake8-comprehensions] NFKC-normalize keyword names in C408 fix (#​26813)
  • [flake8-return] Fix false positive when variable is read in finally clause (RET504) (#​25441)
  • [pydocstyle] Skip section detection inside RST directive bodies (D214, D405, D413) (#​23635)
  • [refurb] Parenthesize yield arguments in the FURB192 fix (#​27192)
Rule changes
  • [flake8-pytest-style] Mark PT022 fixes as unsafe (#​26440)
  • [refurb] Mark fixes that remove unknown separators as unsafe (FURB105) (#​27200)
Server
  • Fix indexing of excluded nested Ruff workspaces (#​27303)
  • Lint TOML files in the LSP (#​26862)
Documentation
  • Cover pycon Markdown formatting (#​27153)
  • [flake8-bandit] Document TYPE_CHECKING exception (S101) (#​27004)
  • [flake8-import-conventions] Document that extend-aliases can override default aliases (#​27191)
  • [pylint] Add missing fix safety gotchas for non-augmented-assignment (PLR6104) (#​27250)
Other changes
  • Reduce syntax error noise by swallowing dedents like indents (#​27170)
  • Vendor latest annotate-snippets (#​27033)
Contributors

v0.16.0

Compare Source

Released on 2026-07-23.

Check out the blog post for a migration
guide and overview of the changes!

Breaking changes
  • Ruff now enables a much larger set of rules by default (413, up from 59). See the blog post for
    more details and the new Default Rules page for a
    full listing of the enabled rules.

  • Ruff can now format Python code blocks in Markdown files and will do this by default. See the
    documentation for more details.

  • Ruff now supports ruff: ignore comments at the ends of lines, like noqa comments, or on the line preceding a diagnostic. For example, these both suppress an unused-import (F401) diagnostic:

    import math  # ruff: ignore[F401]
    
    # ruff: ignore[F401]
    import os
  • Fixes are now shown in check and format --check output:

    ruff format --check .
    unformatted: File would be reformatted
     --> try.md:1:1
      |
    1 | ```python
      - import   math
    2 + import math
    3 | ```
      |
    
    1 file would be reformatted

    This example also shows off the Markdown formatting.

  • format --check now supports the same output formats as the linter, including the github and
    gitlab outputs for rendering annotations in CI:

    ruff format --check --output-format github .
    ::error title=ruff (unformatted),file=try.md,line=2,col=8,endLine=2,endColumn=10::try.md:2:8: unformatted: File would be reformatted

    See the CLI help or documentation for the
    full list of supported formats.

  • The filename, location, end_location, fix.edits[].location, and fix.edits[].end_location
    fields in the JSON output format may now be null rather than defaulting to the empty string and
    row 1, column 1, respectively.

Stabilization

The following rules have been stabilized and are no longer in preview:

The following behaviors have been stabilized:

Preview features
  • [pyupgrade] Fix false positive with TypeVar default before Python 3.13 (UP040) (#​26888)
Bug fixes
  • [ruff] Fix missing check on unrecognized early bound (RUF016) (#​26986)
Rule changes
  • Insert a space after the colon in Ruff suppression comments (#​27123)
Performance
  • [pyupgrade] Speed up unnecessary-future-import (UP010) (#​27047)
Documentation
  • [ruff] Add missing period in "Why is this bad?" section (RUF200) (#​26930)
  • [flake8-simplify] Clarify os.environ behavior on Windows (SIM112) (#​26972)
  • [pydocstyle] Document fix safety (D400) (#​26971)
Contributors

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM — trivial dev-dependency bump.

Extended reasoning...

Overview

This PR only touches requirements-dev.txt, bumping the pinned ruff version from 0.15.21 to 0.15.22 (an autogenerated pip-compile lockfile change). No source code, application logic, or dependency tree structure changes.

Security risks

None. Ruff is a dev-only linting tool, not part of the runtime dependency graph, so this doesn't affect production code paths or attack surface.

Level of scrutiny

Minimal scrutiny is appropriate — this is a routine patch-level bump of a dev tool, generated by Renovate/pip-compile, with only the single version line changed.

Other factors

No CODEOWNER-sensitive paths, no logic changes, no tests needed. Safe to approve without human review.

@renovate renovate Bot changed the title chore(deps): update dependency ruff to v0.15.22 chore(deps): update dependency ruff to v0.15.22 - autoclosed Jul 21, 2026
@renovate renovate Bot closed this Jul 21, 2026
@renovate
renovate Bot deleted the renovate/ruff-0.x branch July 21, 2026 16:03
@renovate renovate Bot changed the title chore(deps): update dependency ruff to v0.15.22 - autoclosed chore(deps): update dependency ruff to v0.16.0 Jul 23, 2026
@renovate renovate Bot reopened this Jul 23, 2026
@renovate
renovate Bot force-pushed the renovate/ruff-0.x branch from 38b5cea to 057e801 Compare July 23, 2026 21:06

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Code review skipped — your organization has reached its monthly code review spending cap.

An organization admin can view or raise the cap at claude.ai/admin-settings/claude-code. The cap resets at the start of the next billing period.

Once the cap resets or is raised, push a new commit or reopen this pull request to trigger a review.

@renovate
renovate Bot force-pushed the renovate/ruff-0.x branch from 057e801 to 38b5cea Compare July 23, 2026 21:06
@renovate renovate Bot changed the title chore(deps): update dependency ruff to v0.16.0 chore(deps): update dependency ruff to v0.16.1 Jul 30, 2026
@renovate
renovate Bot force-pushed the renovate/ruff-0.x branch from 38b5cea to 05109c8 Compare July 30, 2026 22:27

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Code review skipped — your organization's overage spend limit has been reached.

Code review is billed via overage credits. To resume reviews, an organization admin can raise the monthly limit at claude.ai/admin-settings/claude-code.

Once credits are available, push a new commit or reopen this pull request to trigger a review.

@renovate renovate Bot changed the title chore(deps): update dependency ruff to v0.16.1 chore(deps): update dependency ruff to v0.16.2 Aug 7, 2026
@renovate
renovate Bot force-pushed the renovate/ruff-0.x branch from 05109c8 to 59f06bc Compare August 7, 2026 16:48

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM — trivial dev-dependency bump (ruff 0.15.22 → 0.16.2), no runtime impact.

Extended reasoning...

Overview

This PR only touches requirements-dev.txt, an autogenerated pip-compile lockfile, bumping the ruff dev/lint dependency from 0.15.22 to 0.16.2 (and its transitive pin comment). No application source files, no runtime dependencies, and no CI/config files are modified.

Security risks

None. ruff is a linter used only in development/CI, not shipped as part of the pyUSPTO package or executed against untrusted input at runtime. The change is a single version pin bump with no other diff.

Level of scrutiny

Minimal scrutiny is warranted — this is a mechanical, Renovate-generated dependency bump to a single line in a lockfile. Ruff 0.16.x does expand its default rule set significantly, which could surface new lint findings in a future ruff check run, but that would fail visibly in CI/local dev rather than silently breaking anything, and does not affect correctness of the shipped library.

Other factors

File is autogenerated (pip-compile) so there's no hand-written logic to review. No prior review comments on this PR to reconcile. Bug hunting system found no issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants