search

joseffallman / hass_flashforge

FlashForge 3D printer integration for Home Assistant
MIT License
5 stars 2 forks source link

Bump ruff from 0.0.260 to 0.0.275 #13

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps ruff from 0.0.260 to 0.0.275.

Release notes

Sourced from ruff's releases.

v0.0.275

What's Changed

Highlights include a 7-10x decrease in Ruff's cache size.

Rules

Bug Fixes

New Contributors

Full Changelog: https://github.com/astral-sh/ruff/compare/v0.0.274...v0.0.275

v0.0.274

What's Changed

Follow-up release to v0.0.273 to fix a panic in cache accesses.

Bug Fixes

Full Changelog: https://github.com/astral-sh/ruff/compare/v0.0.273...v0.0.274

v0.0.273

What's Changed

Highlights include:

  • Autofix capabilities for rules like flake8-import-conventions, which require symbol renames across a file.
  • Significant decrease in Ruff's cache size (e.g., a ~50% decrease for FastAPI).
  • Dozens and dozens of bug fixes + performance improvements.

... (truncated)

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.

Commits


Dependabot compatibility score

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)
dependabot[bot] commented 1 year ago

Superseded by #14.