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.

Sign up for GitHub

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

Jump to bottom

build(deps): bump ruff from 0.0.263 to 0.0.270 in /.github/workflows #239

Merged
merged 1 commit into from
Jun 1, 2023
Merged

build(deps): bump ruff from 0.0.263 to 0.0.270 in /.github/workflows #239

merged 1 commit into from
Jun 1, 2023

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jun 1, 2023

Bumps ruff from 0.0.263 to 0.0.270.

Release notes

Sourced from ruff's releases.

v0.0.270

What's Changed

Rules

Settings

Bug Fixes

New Contributors

Full Changelog: astral-sh/ruff@v0.0.269...v0.0.270

v0.0.269

... (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.

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
  • 09c50c3 Testing Macros: Add extra-traits feature (#4643)
  • 252506f Remove deprecated --universal2 flag (#4640)
  • f4572fe Bump version to 0.0.270 (#4637)
  • 8c92154 Migrate flake8_bugbear rules to unspecified to suggested (#4616)
  • dcd2bfa Migrate flake8_pie autofix rules from unspecified to suggested and `autom...
  • f0e173d Use BindingId copies in lieu of &BindingId in semantic model methods (#4633)
  • f4f1b1d Only run the playground release job on release (#4636)
  • edc6c40 Move shared_traits to ruff_formatter (#4632)
  • 4233f6e Update to the new rule architecture (#4589)
  • fcdc7bd Remove separate ReferenceContext enum (#4631)
  • Additional commits viewable in compare view

Dependabot compatibility score

You can trigger a rebase of this PR 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
build(deps): bump ruff from 0.0.263 to 0.0.270 in /.github/workflows
61bf939 
Bumps [ruff](https://github.com/charliermarsh/ruff) from 0.0.263 to 0.0.270.
- [Release notes](https://github.com/charliermarsh/ruff/releases)
- [Changelog](https://github.com/charliermarsh/ruff/blob/main/BREAKING_CHANGES.md)
- [Commits](astral-sh/ruff@v0.0.263...v0.0.270)

---
updated-dependencies:
- dependency-name: ruff
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file python Pull requests that update Python code labels Jun 1, 2023
@andros21 andros21 merged commit 0074123 into master Jun 1, 2023
@dependabot dependabot bot deleted the dependabot/pip/dot-github/workflows/ruff-0.0.270 branch June 1, 2023 16:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
dependencies Pull requests that update a dependency file python Pull requests that update Python code
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@andros21