build(deps-dev): bump ruff from 0.1.15 to 0.13.0

[dependabot]

Bumps ruff from 0.1.15 to 0.13.0.

Release notes

Sourced from ruff's releases.

0.13.0

Release Notes

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

Breaking changes

• Several rules can now add from __future__ import annotations automatically

  TC001, TC002, TC003, RUF013, and UP037 now add from __future__ import annotations as part of their fixes when the lint.future-annotations setting is enabled. This allows the rules to move more imports into TYPE_CHECKING blocks (TC001, TC002, and TC003), use PEP 604 union syntax on Python versions before 3.10 (RUF013), and unquote more annotations (UP037).

• Full module paths are now used to verify first-party modules

  Ruff now checks that the full path to a module exists on disk before categorizing it as a first-party import. This change makes first-party import detection more accurate, helping to avoid false positives on local directories with the same name as a third-party dependency, for example. See the FAQ section on import categorization for more details.

• Deprecated rules must now be selected by exact rule code

  Ruff will no longer activate deprecated rules selected by their group name or prefix. As noted below, the two remaining deprecated rules were also removed in this release, so this won't affect any current rules, but it will still affect any deprecations in the future.

• The deprecated macOS configuration directory fallback has been removed

  Ruff will no longer look for a user-level configuration file at ~/Library/Application Support/ruff/ruff.toml on macOS. This feature was deprecated in v0.5 in favor of using the XDG specification (usually resolving to ~/.config/ruff/ruff.toml), like on Linux. The fallback and accompanying deprecation warning have now been removed.

Removed Rules

The following rules have been removed:

• pandas-df-variable-name (PD901)
• non-pep604-isinstance (UP038)

Stabilization

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

• airflow-dag-no-schedule-argument (AIR002)
• airflow3-removal (AIR301)
• airflow3-moved-to-provider (AIR302)
• airflow3-suggested-update (AIR311)
• airflow3-suggested-to-move-to-provider (AIR312)
• long-sleep-not-forever (ASYNC116)
• f-string-number-format (FURB116)
• os-symlink (PTH211)
• generic-not-last-base-class (PYI059)
• redundant-none-literal (PYI061)
• pytest-raises-ambiguous-pattern (RUF043)
• unused-unpacked-variable (RUF059)
• useless-class-metaclass-type (UP050)

The following behaviors have been stabilized:

... (truncated)

Changelog

Sourced from ruff's changelog.

0.13.0

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

Breaking changes

• Several rules can now add from __future__ import annotations automatically

  TC001, TC002, TC003, RUF013, and UP037 now add from __future__ import annotations as part of their fixes when the lint.future-annotations setting is enabled. This allows the rules to move more imports into TYPE_CHECKING blocks (TC001, TC002, and TC003), use PEP 604 union syntax on Python versions before 3.10 (RUF013), and unquote more annotations (UP037).

• Full module paths are now used to verify first-party modules

  Ruff now checks that the full path to a module exists on disk before categorizing it as a first-party import. This change makes first-party import detection more accurate, helping to avoid false positives on local directories with the same name as a third-party dependency, for example. See the FAQ section on import categorization for more details.

• Deprecated rules must now be selected by exact rule code

  Ruff will no longer activate deprecated rules selected by their group name or prefix. As noted below, the two remaining deprecated rules were also removed in this release, so this won't affect any current rules, but it will still affect any deprecations in the future.

• The deprecated macOS configuration directory fallback has been removed

  Ruff will no longer look for a user-level configuration file at ~/Library/Application Support/ruff/ruff.toml on macOS. This feature was deprecated in v0.5 in favor of using the XDG specification (usually resolving to ~/.config/ruff/ruff.toml), like on Linux. The fallback and accompanying deprecation warning have now been removed.

Removed Rules

The following rules have been removed:

• pandas-df-variable-name (PD901)
• non-pep604-isinstance (UP038)

Stabilization

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

... (truncated)

Commits

• a1fdd66 Bump 0.13.0 (#20336)
• 8770b95 [ty] introduce DivergentType (#20312)
• 65982a1 [ty] Use 'unknown' specialization for upper bound on Self (#20325)
• 57d1f71 [ty] Simplify unions of enum literals and subtypes thereof (#20324)
• 7a75702 Ignore deprecated rules unless selected by exact code (#20167)
• 9ca632c Stabilize adding future import via config option (#20277)
• 64fe7d3 [flake8-errmsg] Stabilize extending raw-string-in-exception (EM101) to ...
• beeeb8d Stabilize the remaining Airflow rules (#20250)
• b6fca52 [flake8-bugbear] Stabilize support for non-context-manager calls in `assert...
• ac7f882 [flake8-commas] Stabilize support for trailing comma checks in type paramet...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[kishore7snehil]

@dependabot ignore

[dependabot]

Sorry, the command you entered is not valid for this pull request. Please check the syntax and try again.

Valid commands:
For single dependency PRs, use commands like:
@dependabot ignore this major version
@dependabot ignore this minor version
@dependabot ignore this dependency

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.