Skip to content

feat: allow Ruff 0.11 #1222

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 15, 2025
Merged

feat: allow Ruff 0.11 #1222

merged 1 commit into from
Mar 15, 2025

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 14, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
ruff (source, changelog) >=0.2,<0.11 -> >=0.2,<0.12 age adoption passing confidence

Release Notes

astral-sh/ruff (ruff)

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)

Configuration

📅 Schedule: 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 is behind base branch, 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.

@johnthagen johnthagen mentioned this pull request Mar 14, 2025
@dbanty dbanty changed the title chore(deps): update dependency ruff to >=0.2,<0.12 feat: support Ruff 0.11 Mar 15, 2025
@dbanty dbanty changed the title feat: support Ruff 0.11 feat: allow Ruff 0.11 Mar 15, 2025
@dbanty dbanty added this pull request to the merge queue Mar 15, 2025
Merged via the queue into main with commit 25fe48e Mar 15, 2025
22 checks passed
@dbanty dbanty deleted the renovate/ruff-0.x branch March 15, 2025 16:43
github-merge-queue bot pushed a commit that referenced this pull request Mar 15, 2025
> [!IMPORTANT]
> Merging this pull request will create this release

## Features

- allow Ruff to 0.10 (#1220)
- allow Ruff 0.11 (#1222)
- Allow any `Mapping` in generated `from_dict` functions (#1211)

## Fixes

### Always parse `$ref` as a reference

If additional attributes were included with a `$ref` (for example
`title` or `description`), the property could be
interpreted as a new type instead of a reference, usually resulting in
`Any` in the generated code.
Now, any sibling properties to `$ref` will properly be ignored, as per
the OpenAPI specification.

Thanks @nkrishnaswami!

Co-authored-by: knope-bot[bot] <152252888+knope-bot[bot]@users.noreply.github.com>
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.

1 participant