Bump ruff from 0.7.2 to 0.7.3 #11222
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps [ruff](https://github.com/astral-sh/ruff) from 0.7.2 to 0.7.3. - [Release notes](https://github.com/astral-sh/ruff/releases) - [Changelog](https://github.com/astral-sh/ruff/blob/main/CHANGELOG.md) - [Commits](astral-sh/ruff@0.7.2...0.7.3) --- updated-dependencies: - dependency-name: ruff dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
dependencies
DryRun Security SummaryThe code change in this GitHub Pull Request is a routine update to the version of the "ruff" linting tool dependency in the "requirements-lint.txt" file, which should be approved after reviewing the changelog and thoroughly testing the application. Expand for full summarySummary: The code change in this GitHub Pull Request is a routine update to the version of the "ruff" linting tool dependency in the "requirements-lint.txt" file. Updating linting tool dependencies is generally a positive change, as it can include bug fixes, performance improvements, and the ability to detect additional security issues in the codebase. However, it's important to review the changelog or release notes for the "ruff" version update to understand the specific changes and ensure that there are no known security vulnerabilities or breaking changes introduced in the new version. Additionally, it's a good practice to thoroughly test the application after such a dependency update to verify that the linting process and the application's functionality remain intact. Overall, this code change seems routine and does not raise any immediate security concerns. As an application security engineer, I would recommend approving the Pull Request, provided that the necessary testing and review of the "ruff" version update have been completed. Files Changed:
Code AnalysisWe ran Riskiness🟢 Risk threshold not exceeded. |
1 similar comment
DryRun Security SummaryThe code change in this GitHub Pull Request is a routine update to the version of the "ruff" linting tool dependency in the "requirements-lint.txt" file, which should be approved after reviewing the changelog and thoroughly testing the application. Expand for full summarySummary: The code change in this GitHub Pull Request is a routine update to the version of the "ruff" linting tool dependency in the "requirements-lint.txt" file. Updating linting tool dependencies is generally a positive change, as it can include bug fixes, performance improvements, and the ability to detect additional security issues in the codebase. However, it's important to review the changelog or release notes for the "ruff" version update to understand the specific changes and ensure that there are no known security vulnerabilities or breaking changes introduced in the new version. Additionally, it's a good practice to thoroughly test the application after such a dependency update to verify that the linting process and the application's functionality remain intact. Overall, this code change seems routine and does not raise any immediate security concerns. As an application security engineer, I would recommend approving the Pull Request, provided that the necessary testing and review of the "ruff" version update have been completed. Files Changed:
Code AnalysisWe ran Riskiness🟢 Risk threshold not exceeded. |
|
I fixed the ruff linter and ruff update here: #11224 |
|
This can be closed @mtesauro |
|
@dependabot rebase |
|
Looks like ruff is up-to-date now, so this is no longer needed. |
Bumps ruff from 0.7.2 to 0.7.3.
Release notes
Sourced from ruff's releases.
... (truncated)
Changelog
Sourced from ruff's changelog.
Commits
fbf140aBump version to 0.7.3 (#14197)670f958[red-knot] Fix intersection simplification for~Any/~Unknown(#14195)fed35a2[red-knot] Fixis_assignable_tofor unions (#14196)d1ef418Docs: tweak rules documentation (#14180)272d24b[flake8-pyi] Add a fix forduplicate-literal-member(#14188)2624249[red-knot] Minor: fixLiteral[True] <: int(#14177)4b08d17[red-knot] Add a newType::KnownInstanceTypevariant (#14155)5b6169b[red-knot] Minor fix in intersection type comment (#14176)2040e93[flake8-logging-format] Fix invalid formatting value in docs of `logging-ex...794eb88[flake8-bandit] Typo in docssuspicious-pickle-import(S403) (#14175)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)