Skip to content
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

fix(deps): update ruff to v0.11.0 #6

Merged
merged 1 commit into from
Mar 14, 2025
Merged

Conversation

pactflow-renovate-bot[bot]
Copy link
Contributor

This PR contains the following updates:

Package Type Update Change
astral-sh/ruff-pre-commit repository minor v0.10.0 -> v0.11.0
ruff (source, changelog) project.optional-dependencies minor ==0.10.0 -> ==0.11.0

Note: The pre-commit manager in Renovate is not supported by the pre-commit maintainers or community. Please do not report any problems there, instead create a Discussion in the Renovate repository if you have any questions.


Release Notes

astral-sh/ruff-pre-commit (astral-sh/ruff-pre-commit)

v0.11.0

Compare Source

See: https://github.com/astral-sh/ruff/releases/tag/0.11.0

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: Enabled.

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 these updates again.


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

This PR has been generated by Renovate Bot.

@pactflow-renovate-bot pactflow-renovate-bot bot merged commit a6f6beb into main Mar 14, 2025
12 checks passed
@pactflow-renovate-bot pactflow-renovate-bot bot deleted the gh-renovate/ruff branch March 14, 2025 15:25
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