Skip to content

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 2, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
ruff (source, changelog) ^0.9.4 -> ^0.11.0 age adoption passing confidence

Release Notes

astral-sh/ruff (ruff)

v0.11.3

Compare Source

Preview features
  • [airflow] Add more autofixes for AIR302 (#​16876, #​16977, #​16976, #​16965)
  • [airflow] Move AIR301 to AIR002 (#​16978)
  • [airflow] Move AIR302 to AIR301 and AIR303 to AIR302 (#​17151)
  • [flake8-bandit] Mark str and list[str] literals as trusted input (S603) (#​17136)
  • [ruff] Support slices in RUF005 (#​17078)
  • [syntax-errors] Start detecting compile-time syntax errors (#​16106)
  • [syntax-errors] Duplicate type parameter names (#​16858)
  • [syntax-errors] Irrefutable case pattern before final case (#​16905)
  • [syntax-errors] Multiple assignments in case pattern (#​16957)
  • [syntax-errors] Single starred assignment target (#​17024)
  • [syntax-errors] Starred expressions in return, yield, and for (#​17134)
  • [syntax-errors] Store to or delete __debug__ (#​16984)
Bug fixes
  • Error instead of panic! when running Ruff from a deleted directory (#​16903) (#​17054)
  • [syntax-errors] Fix false positive for parenthesized tuple index (#​16948)
CLI
  • Check pyproject.toml correctly when it is passed via stdin (#​16971)
Configuration
  • [flake8-import-conventions] Add import numpy.typing as npt to default flake8-import-conventions.aliases (#​17133)
Documentation
  • [refurb] Document why UserDict, UserList, and UserString are preferred over dict, list, and str (FURB189) (#​16927)

v0.11.2

Compare Source

Preview features
  • [syntax-errors] Fix false-positive syntax errors emitted for annotations on variadic parameters before Python 3.11 (#​16878)

v0.11.1

Compare Source

Preview features
  • [airflow] Add chain, chain_linear and cross_downstream for AIR302 (#​16647)
  • [syntax-errors] Improve error message and range for pre-PEP-614 decorator syntax errors (#​16581)
  • [syntax-errors] PEP 701 f-strings before Python 3.12 (#​16543)
  • [syntax-errors] Parenthesized context managers before Python 3.9 (#​16523)
  • [syntax-errors] Star annotations before Python 3.11 (#​16545)
  • [syntax-errors] Star expression in index before Python 3.11 (#​16544)
  • [syntax-errors] Unparenthesized assignment expressions in sets and indexes (#​16404)
Bug fixes
  • Server: Allow FixAll action in presence of version-specific syntax errors (#​16848)
  • [flake8-bandit] Allow raw strings in suspicious-mark-safe-usage (S308) #​16702 (#​16770)
  • [refurb] Avoid panicking unwrap in verbose-decimal-constructor (FURB157) (#​16777)
  • [refurb] Fix starred expressions fix (FURB161) (#​16550)
  • Fix --statistics reporting for unsafe fixes (#​16756)
Rule changes
  • [flake8-executables] Allow uv run in shebang line for shebang-missing-python (EXE003) (#​16849,#​16855)
CLI
Documentation
  • Update Ruff tutorial to avoid non-existent fix in __init__.py (#​16818)
  • [flake8-gettext] Swap format- and printf-in-get-text-func-call examples (INT002, INT003) (#​16769)

v0.11.0

Compare Source

This is a follow-up to release 0.10.0. Because of a mistake in the release process, the requires-python inference changes were not included in that release. Ruff 0.11.0 now includes this change as well as the stabilization of the preview behavior for PGH004.

Breaking changes
  • Changes to how the Python version is inferred when a target-version is not specified (#​16319)

    In previous versions of Ruff, you could specify your Python version with:

    • The target-version option in a ruff.toml file or the [tool.ruff] section of a pyproject.toml file.
    • The project.requires-python field in a pyproject.toml file with a [tool.ruff] section.

    These options worked well in most cases, and are still recommended for fine control of the Python version. However, because of the way Ruff discovers config files, pyproject.toml files without a [tool.ruff] section would be ignored, including the requires-python setting. Ruff would then use the default Python version (3.9 as of this writing) instead, which is surprising when you've attempted to request another version.

    In v0.10, config discovery has been updated to address this issue:

    • If Ruff finds a ruff.toml file without a target-version, it will check
      for a pyproject.toml file in the same directory and respect its
      requires-python version, even if it does not contain a [tool.ruff]
      section.
    • If Ruff finds a user-level configuration, the requires-python field of the closest pyproject.toml in a parent directory will take precedence.
    • If there is no config file (ruff.tomlor pyproject.toml with a
      [tool.ruff] section) in the directory of the file being checked, Ruff will
      search for the closest pyproject.toml in the parent directories and use its
      requires-python setting.
Stabilization

The following behaviors have been stabilized:

  • blanket-noqa (PGH004): Also detect blanked file-level noqa comments (and not just line level comments).
Preview features
  • [syntax-errors] Tuple unpacking in for statement iterator clause before Python 3.9 (#​16558)

v0.10.0

Compare Source

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

Breaking changes

See also, the "Remapped rules" section which may result in disabled rules.

  • Changes to how the Python version is inferred when a target-version is not specified (#​16319)

    Because of a mistake in the release process, the requires-python inference changes are not included in this release and instead shipped as part of 0.11.0.
    You can find a description of this change in the 0.11.0 section.

  • Updated TYPE_CHECKING behavior (#​16669)

    Previously, Ruff only recognized typechecking blocks that tested the typing.TYPE_CHECKING symbol. Now, Ruff recognizes any local variable named TYPE_CHECKING. This release also removes support for the legacy if 0: and if False: typechecking checks. Use a local TYPE_CHECKING variable instead.

  • More robust noqa parsing (#​16483)

    The syntax for both file-level and in-line suppression comments has been unified and made more robust to certain errors. In most cases, this will result in more suppression comments being read by Ruff, but there are a few instances where previously read comments will now log an error to the user instead. Please refer to the documentation on Error suppression for the full specification.

  • Avoid unnecessary parentheses around with statements with a single context manager and a trailing comment (#​14005)

    This change fixes a bug in the formatter where it introduced unnecessary parentheses around with statements with a single context manager and a trailing comment. This change may result in a change in formatting for some users.

  • Bump alpine default tag to 3.21 for derived Docker images (#​16456)

    Alpine 3.21 was released in Dec 2024 and is used in the official Alpine-based Python images. Now the ruff:alpine image will use 3.21 instead of 3.20 and ruff:alpine3.20 will no longer be updated.

Deprecated Rules

The following rules have been deprecated:

Remapped rules

The following rules have been remapped to new rule codes:

  • [unsafe-markup-use]: RUF035 to S704
Stabilization

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

The following behaviors have been stabilized:

The following fixes or improvements to fixes have been stabilized:

Server
  • Remove logging output for ruff.printDebugInformation (#​16617)
Configuration
  • [flake8-builtins] Deprecate the builtins- prefixed options in favor of the unprefixed options (e.g. builtins-allowed-modules is now deprecated in favor of allowed-modules) (#​16092)
Bug fixes
  • [flake8-bandit] Fix mixed-case hash algorithm names (S324) (#​16552)
CLI
  • [ruff] Fix last_tag/commits_since_last_tag for version command (#​16686)

v0.9.10

Compare Source

Preview features
  • [ruff] Add new rule RUF059: Unused unpacked assignment (#​16449)
  • [syntax-errors] Detect assignment expressions before Python 3.8 (#​16383)
  • [syntax-errors] Named expressions in decorators before Python 3.9 (#​16386)
  • [syntax-errors] Parenthesized keyword argument names after Python 3.8 (#​16482)
  • [syntax-errors] Positional-only parameters before Python 3.8 (#​16481)
  • [syntax-errors] Tuple unpacking in return and yield before Python 3.8 (#​16485)
  • [syntax-errors] Type parameter defaults before Python 3.13 (#​16447)
  • [syntax-errors] Type parameter lists before Python 3.12 (#​16479)
  • [syntax-errors] except* before Python 3.11 (#​16446)
  • [syntax-errors] type statements before Python 3.12 (#​16478)
Bug fixes
  • Escape template filenames in glob patterns in configuration (#​16407)
  • [flake8-simplify] Exempt unittest context methods for SIM115 rule (#​16439)
  • Formatter: Fix syntax error location in notebooks (#​16499)
  • [pyupgrade] Do not offer fix when at least one target is global/nonlocal (UP028) (#​16451)
  • [flake8-builtins] Ignore variables matching module attribute names (A001) (#​16454)
  • [pylint] Convert code keyword argument to a positional argument in fix for (PLR1722) (#​16424)
CLI
  • Move rule code from description to check_name in GitLab output serializer (#​16437)
Documentation
  • [pydocstyle] Clarify that D417 only checks docstrings with an arguments section (#​16494)

Configuration

📅 Schedule: Branch creation - "after 5pm on the 2nd day of the month" (UTC), 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.

@zml2008 zml2008 self-assigned this Apr 6, 2025
@zml2008 zml2008 merged commit c4f72da into trunk Apr 6, 2025
8 checks passed
@renovate renovate bot deleted the renovate/ruff-0.x branch April 6, 2025 00:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant