Bump ruff from 0.15.14 to 0.15.18#228
Merged
Merged
Conversation
Bumps [ruff](https://github.com/astral-sh/ruff) from 0.15.14 to 0.15.18. - [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.15.14...0.15.18) --- updated-dependencies: - dependency-name: ruff dependency-version: 0.15.18 dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
rtibblesbot
approved these changes
Jul 1, 2026
rtibblesbot
left a comment
rtibblesbot
left a comment
Contributor
There was a problem hiding this comment.
Routine patch bump of the ruff linter.
- Package:
ruff0.15.14 → 0.15.18 (devDependency,pyproject.toml:42) - Semver risk: Patch
- Breaking changes: None.
- Security fixes: None.
- Notable changes: Preview-feature additions, bug fixes, performance/parser fixes, and a preview-only rule rename (
PYI033→legacy-type-comment, not enabled in this project's config). - Diff:
uv.lockonly (version/hashes forruff), no other packages touched. Project's ruff config (pyproject.toml:54-61) doesn't reference any changed rules. - CI: Passing, including the file-linting check that runs this exact ruff version.
No blocking issues.
@rtibblesbot's comments are generated by an LLM, and should be evaluated accordingly
How was this generated?
Ran a dependency-update review pipeline over the version bump:
- Classified the bump by semver (patch / minor / major) and dependency type (production vs. development)
- Extracted the changelog and release notes across the version range
- Assessed compatibility with this project's usage and whether any code changes are required
- Treated CI as the primary safety net
- Scaled the review depth to the update's risk
- Chose the verdict from semver risk, changelog findings, and CI status
rtibbles
approved these changes
Jul 1, 2026
rtibbles
left a comment
rtibbles
left a comment
Member
There was a problem hiding this comment.
No concerns from changelog or diff.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps ruff from 0.15.14 to 0.15.18.
Release notes
Sourced from ruff's releases.
... (truncated)
Changelog
Sourced from ruff's changelog.
... (truncated)
Commits
6686f63Bump 0.15.18 (#26135)efbb732[ty] Suggest keyword-only arguments between variadic parameters (#26134)c256d5f[ty] SupportAnnotated[Any, ...]as a class base (#26133)19a4bea[flake8-pyi] Rename PYI033 to legacy-type-comment (#26131)1d9866cBump ecosystem-analyzer commit (#26130)8656c73[ty] Compact indexed AST node storage (#25998)c17c8d9[ty] Garbage-collect cached constraint sets (#26116)ef0fb8f[ty] Fix bound TypeVar default cycle recovery (#26124)b83c024[flake8-pyi] Extend PYI033 to Python files in preview (#26129)e8a5e38Update Rust crate zip to v8 (#26078)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 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)