chore(deps-dev): update ruff requirement from >=0.0.192,<0.0.271 to >=0.0.192,<0.0.273

[dependabot]

Updates the requirements on ruff to permit the latest version.

Release notes

Sourced from ruff's releases.

v0.0.272

What's Changed

Breaking Changes

• Move flake8-fixme rules to FIX prefix by @​charliermarsh in charliermarsh/ruff#4917

Rules

• [flake8-pyi] Implement PYI050 by @​density in charliermarsh/ruff#4884

Bug Fixes

• Avoid attributing runtime references to module-level imports by @​charliermarsh in charliermarsh/ruff#4942
• Skip class scopes when resolving nonlocal references by @​charliermarsh in charliermarsh/ruff#4943
• Apply dict.get fix before ternary rewrite by @​charliermarsh in charliermarsh/ruff#4944
• Handle implicit string concatenations in conversion-flag rewrites by @​charliermarsh in charliermarsh/ruff#4947
• Make C413 fix as suggested for reversed call by @​dhruvmanila in charliermarsh/ruff#4891
• ignore if using infinite iterators in B905 by @​kyoto7250 in charliermarsh/ruff#4914

Full Changelog: astral-sh/ruff@v0.0.271...v0.0.272

Changelog

Sourced from ruff's changelog.

Breaking Changes

0.0.268

The keep-runtime-typing setting has been removed (#4427)

Enabling the keep-runtime-typing option, located under the pyupgrade section, is equivalent to ignoring the UP006 and UP007 rules via Ruff's standard ignore mechanism. As there's no need for a dedicated setting to disable these rules, the keep-runtime-typing option has been removed.

0.0.267

update-check is no longer a valid configuration option (#4313)

The update-check functionality was deprecated in #2530, in that the behavior itself was removed, and Ruff was changed to warn when that option was enabled.

Now, Ruff will throw an error when update-check is provided via a configuration file (e.g., update-check = false) or through the command-line, since it has no effect. Users should remove this option from their configuration.

0.0.265

--fix-only now exits with a zero exit code, unless --exit-non-zero-on-fix is specified (#4146)

Previously, --fix-only would exit with a non-zero exit code if any fixes were applied. This behavior was inconsistent with --fix, and further, meant that --exit-non-zero-on-fix was effectively ignored when --fix-only was specified.

Now, --fix-only will exit with a zero exit code, unless --exit-non-zero-on-fix is specified, in which case it will exit with a non-zero exit code if any fixes were applied.

0.0.260

Fixes are now represented as a list of edits (#3709)

Previously, Ruff represented each fix as a single edit, which prohibited Ruff from automatically fixing violations that required multiple edits across a file. As such, Ruff now represents each fix as a list of edits.

This primarily affects the JSON API. Ruff's JSON representation used to represent the fix field as a single edit, like so:

{
    "message": "Remove unused import: `sys`",
    "content": "",
    "location": {"row": 1, "column": 0},
    "end_location": {"row": 2, "column": 0}
</tr></table> 

... (truncated)

Commits

• 4b78141 Generate one fix per statement for flake8-type-checking rules (#4915)
• 5235977 Bump version to 0.0.272 (#4948)
• 01d3d4b ignore if using infinite iterators in B905 (#4914)
• ac4a4da Handle implicit string concatenations in conversion-flag rewrites (#4947)
• a6d269f Apply dict.get fix before ternary rewrite (#4944)
• f17282d Skip class scopes when resolving nonlocal references (#4943)
• 6950c93 Make C413 fix as suggested for reversed call (#4891)
• ae75b30 Avoid attributing runtime references to module-level imports (#4942)
• 20240fc Move flake8-fixme rules to FIX prefix (#4917)
• f990d9d Remove libafl_libfuzzer while it remains unstable (#4933)
• 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 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)

[codecov]

Codecov Report

Patch and project coverage have no change.

Comparison is base (55c111b) 93.90% compared to head (d114718) 93.90%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #59   +/-   ##
=======================================
  Coverage   93.90%   93.90%           
=======================================
  Files           5        5           
  Lines         197      197           
=======================================
  Hits          185      185           
  Misses         12       12           

Flag	Coverage Δ
unittests	93.90% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.