[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
ruff	==0.17.0 → ==0.17.3

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[claude]

LGTM, straightforward version bump. Reviewed: the single-line change to requirements-dev.txt bumping the pinned ruff dev dependency from 0.17.0 to 0.17.1, with the lockfile comment ("via pyuspto") left intact.

Extended reasoning...

The diff touches only requirements-dev.txt, bumping a pinned dev-only linter (ruff) by one patch version; no source code, build config, or security-sensitive surface is affected. This is a mechanical Renovate-generated dependency bump with no ambiguity and no CODEOWNERS concerns, so no human review is needed.

[claude]

LGTM. This is a patch-level bump of a dev-only linter pin.

What was reviewed:

• requirements-dev.txt now pins ruff==0.17.2 instead of 0.17.0. Nothing else in the lockfile changes.
• The new pin still satisfies the source constraint ruff>=0.15.0 in the lint extra of pyproject.toml.
• Ruff only runs as a linter and formatter (CI ruff check / ruff format --check), so the package's runtime dependencies are unaffected.

Extended reasoning...

The change is one line in requirements-dev.txt, moving the dev-only ruff pin from 0.17.0 to 0.17.2. The pin still satisfies the ruff>=0.15.0 constraint in pyproject.toml. It touches no security-sensitive code (no auth, injection or data-exposure paths) and no runtime dependencies. There are no CODEOWNERS or ANTOWNERS files, and no other reviewer has left an open objection. A new commit landed after the earlier review, and the change is small and mechanical, so approval is appropriate. Any new lint findings from the upgrade would show up in the existing CI ruff steps.

[claude]

⚠️ Code review skipped — your organization's remaining monthly code review budget is too low to start another review, so this review was not started.

An organization admin can view or raise the monthly spending cap at claude.ai/admin-settings/usage, on the Claude Code Review row under Services. The cap resets at the start of the next billing period.

Once the cap resets or is raised, someone with write access to this repository can comment @claude review on this pull request to trigger a review.