Skip to content

Update dependency ruff to >=0.16.1 - #2768

Merged
mergify[bot] merged 1 commit into
mainfrom
renovate/ruff-0.x
Aug 3, 2026
Merged

mergify[bot] merged 1 commit into
mainfrom
renovate/ruff-0.x

Conversation

@renovate

@renovate renovate Bot commented Jul 30, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
ruff (source, changelog) >=0.16.0 → >=0.16.1 age confidence

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 is behind base branch, 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.

@renovate
renovate Bot temporarily deployed to code_quality July 30, 2026 22:57 Inactive
@renovate
renovate Bot temporarily deployed to code_quality July 30, 2026 22:57 Inactive
@renovate
renovate Bot temporarily deployed to code_quality July 30, 2026 22:57 Inactive
@renovate
renovate Bot temporarily deployed to code_quality July 30, 2026 22:57 Inactive
@renovate
renovate Bot temporarily deployed to code_quality July 30, 2026 22:57 Inactive
@renovate
renovate Bot temporarily deployed to code_quality July 30, 2026 22:57 Inactive
@renovate
renovate Bot temporarily deployed to code_quality July 30, 2026 22:57 Inactive
@renovate
renovate Bot temporarily deployed to code_quality July 30, 2026 22:57 Inactive
@renovate
renovate Bot temporarily deployed to code_quality July 30, 2026 22:57 Inactive
@renovate
renovate Bot temporarily deployed to code_quality July 30, 2026 22:57 Inactive
@renovate
renovate Bot temporarily deployed to code_quality July 30, 2026 22:57 Inactive
@renovate
renovate Bot temporarily deployed to code_quality July 30, 2026 22:57 Inactive
@renovate
renovate Bot temporarily deployed to docker_image July 30, 2026 22:58 Inactive
@mergify mergify Bot added dependencies Pull requests that update a dependency file python uv labels Jul 30, 2026
@mergify

mergify Bot commented Jul 30, 2026 •

Copy link
Copy Markdown
Contributor

Merge Queue Status

This pull request spent 4 minutes 48 seconds in the queue, including 4 minutes 21 seconds running CI.

Waiting for
  • check-success = Test Image / API Test
All conditions
  • check-success = Test Image / API Test
  • github-review-approved [🛡 GitHub repository ruleset rule main]
  • any of [🛡 GitHub repository ruleset rule main]:
    • check-neutral = @mergify/Mergify Merge Protections
    • check-skipped = @mergify/Mergify Merge Protections
    • check-success = @mergify/Mergify Merge Protections

Reason

The merge conditions cannot be satisfied due to failing checks

  • Test Image / API Test
  • @mergify/Mergify Merge Protections

Failing checks:

Hint

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

Requeued — the merge queue status continues in this comment ↓.

@mergify mergify Bot added the queued label Jul 30, 2026
@renovate
renovate Bot temporarily deployed to container_health July 30, 2026 23:01 Inactive
@mergify

mergify Bot commented Aug 1, 2026 •

Copy link
Copy Markdown
Contributor

Merge Queue Status

This pull request spent 3 minutes 50 seconds in the queue, with no time running CI.

Waiting for
  • check-success = Test Image / API Test
  • any of: [🛡 GitHub repository ruleset rule main]
    • check-neutral = @mergify/Mergify Merge Protections
    • check-skipped = @mergify/Mergify Merge Protections
    • check-success = @mergify/Mergify Merge Protections
All conditions
  • check-success = Test Image / API Test
  • any of [🛡 GitHub repository ruleset rule main]:
    • check-neutral = @mergify/Mergify Merge Protections
    • check-skipped = @mergify/Mergify Merge Protections
    • check-success = @mergify/Mergify Merge Protections
  • github-review-approved [🛡 GitHub repository ruleset rule main]

Reason

The pull request #2768 has been manually updated

Requeued — the merge queue status continues in this comment ↓.

@mergify

mergify Bot commented Aug 1, 2026 •

Copy link
Copy Markdown
Contributor

Merge Queue Status

This pull request spent 16 minutes 44 seconds in the queue, including 16 minutes running CI.

Waiting for
  • check-success = Test Image / API Test
All conditions
  • check-success = Test Image / API Test
  • github-review-approved [🛡 GitHub repository ruleset rule main]
  • any of [🛡 GitHub repository ruleset rule main]:
    • check-neutral = @mergify/Mergify Merge Protections
    • check-skipped = @mergify/Mergify Merge Protections
    • check-success = @mergify/Mergify Merge Protections

Reason

The merge conditions cannot be satisfied due to failing checks

  • Test Image / API Test
  • @mergify/Mergify Merge Protections

Failing checks:

Hint

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

Requeued — the merge queue status continues in this comment ↓.

@mergify

mergify Bot commented Aug 1, 2026

Copy link
Copy Markdown
Contributor

Hey @renovate[bot], your pull request has been dequeued due to the following reason: CHECKS_FAILED. Sorry about that, but you can requeue the PR by using @mergifyio requeue if you think this was a mistake.

@mergify

mergify Bot commented Aug 2, 2026 •

Copy link
Copy Markdown
Contributor

Merge Queue Status

This pull request spent 2 minutes 35 seconds in the queue, with no time running CI.

Waiting for
  • check-success = Test Image / API Test
  • any of: [🛡 GitHub repository ruleset rule main]
    • check-neutral = @mergify/Mergify Merge Protections
    • check-skipped = @mergify/Mergify Merge Protections
    • check-success = @mergify/Mergify Merge Protections
All conditions
  • check-success = Test Image / API Test
  • any of [🛡 GitHub repository ruleset rule main]:
    • check-neutral = @mergify/Mergify Merge Protections
    • check-skipped = @mergify/Mergify Merge Protections
    • check-success = @mergify/Mergify Merge Protections
  • github-review-approved [🛡 GitHub repository ruleset rule main]

Reason

The pull request #2768 has been manually updated

Requeued — the merge queue status continues in this comment ↓.

@mergify

mergify Bot commented Aug 2, 2026 •

Copy link
Copy Markdown
Contributor

Merge Queue Status

This pull request spent 2 minutes 53 seconds in the queue, with no time running CI.

Waiting for
  • check-success = Test Image / API Test
  • any of: [🛡 GitHub repository ruleset rule main]
    • check-neutral = @mergify/Mergify Merge Protections
    • check-skipped = @mergify/Mergify Merge Protections
    • check-success = @mergify/Mergify Merge Protections
All conditions
  • check-success = Test Image / API Test
  • any of [🛡 GitHub repository ruleset rule main]:
    • check-neutral = @mergify/Mergify Merge Protections
    • check-skipped = @mergify/Mergify Merge Protections
    • check-success = @mergify/Mergify Merge Protections
  • github-review-approved [🛡 GitHub repository ruleset rule main]

Reason

The pull request #2768 has been manually updated

Requeued — the merge queue status continues in this comment ↓.

@mergify

mergify Bot commented Aug 2, 2026 •

Copy link
Copy Markdown
Contributor

Merge Queue Status

This pull request spent 10 minutes 32 seconds in the queue, including 10 minutes running CI.

Waiting for
  • check-success = Test Image / API Test
All conditions
  • check-success = Test Image / API Test
  • github-review-approved [🛡 GitHub repository ruleset rule main]
  • any of [🛡 GitHub repository ruleset rule main]:
    • check-neutral = @mergify/Mergify Merge Protections
    • check-skipped = @mergify/Mergify Merge Protections
    • check-success = @mergify/Mergify Merge Protections

Reason

The merge conditions cannot be satisfied due to failing checks

  • Test Image / API Test
  • @mergify/Mergify Merge Protections

Failing checks:

Hint

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

Requeued — the merge queue status continues in this comment ↓.

@mergify

mergify Bot commented Aug 2, 2026

Copy link
Copy Markdown
Contributor

Hey @renovate[bot], your pull request has been dequeued due to the following reason: CHECKS_FAILED. Sorry about that, but you can requeue the PR by using @mergifyio requeue if you think this was a mistake.

@mergify

mergify Bot commented Aug 3, 2026 •

Copy link
Copy Markdown
Contributor

Merge Queue Status

This pull request spent 2 minutes 20 seconds in the queue, with no time running CI.

Reason

The pull request #2768 has been manually updated

Requeued — the merge queue status continues in this comment ↓.

@mergify

mergify Bot commented Aug 3, 2026 •

Copy link
Copy Markdown
Contributor

Merge Queue Status

This pull request spent 13 minutes 40 seconds in the queue, including 12 minutes 16 seconds running CI.

Waiting for
  • check-success = Test Image / API Test
All conditions
  • check-success = Test Image / API Test
  • github-review-approved [🛡 GitHub repository ruleset rule main]
  • any of [🛡 GitHub repository ruleset rule main]:
    • check-neutral = @mergify/Mergify Merge Protections
    • check-skipped = @mergify/Mergify Merge Protections
    • check-success = @mergify/Mergify Merge Protections

Reason

The merge conditions cannot be satisfied due to failing checks

  • Test Image / API Test
  • @mergify/Mergify Merge Protections

Failing checks:

Hint

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

Requeued — the merge queue status continues in this comment ↓.

@mergify

mergify Bot commented Aug 3, 2026 •

Copy link
Copy Markdown
Contributor

Merge Queue Status

This pull request spent 4 minutes 35 seconds in the queue, with no time running CI.

Waiting for
  • check-success = Test Image / API Test
  • any of: [🛡 GitHub repository ruleset rule main]
    • check-neutral = @mergify/Mergify Merge Protections
    • check-skipped = @mergify/Mergify Merge Protections
    • check-success = @mergify/Mergify Merge Protections
All conditions
  • check-success = Test Image / API Test
  • any of [🛡 GitHub repository ruleset rule main]:
    • check-neutral = @mergify/Mergify Merge Protections
    • check-skipped = @mergify/Mergify Merge Protections
    • check-success = @mergify/Mergify Merge Protections
  • github-review-approved [🛡 GitHub repository ruleset rule main]

Reason

The pull request #2768 has been manually updated

Requeued — the merge queue status continues in this comment ↓.

@sonarqubecloud

sonarqubecloud Bot commented Aug 3, 2026

Copy link
Copy Markdown

@mergify

mergify Bot commented Aug 3, 2026 •

Copy link
Copy Markdown
Contributor

Merge Queue Status

This pull request spent 16 minutes 46 seconds in the queue, including 15 minutes 56 seconds running CI.

Required conditions to merge
  • check-success = Test Image / API Test
  • github-review-approved [🛡 GitHub repository ruleset rule main]
  • any of [🛡 GitHub repository ruleset rule main]:
    • check-neutral = @mergify/Mergify Merge Protections
    • check-skipped = @mergify/Mergify Merge Protections
    • check-success = @mergify/Mergify Merge Protections

@mergify

mergify Bot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

Thank you for your contribution @renovate[bot]! Your pull request has been merged.

This branch had an error being deployed

2 failed and 1 inactive deployments
docker_image — c6f4aa2c Deployed Aug 3, 2026 by renovate[bot] via Test Image / Cleaning GHCR #11476
code_quality — c6f4aa2c Deployed Aug 3, 2026 by renovate[bot] via Lint / pre-commit #11476
container_health — c6f4aa2c Deployed Aug 3, 2026 by renovate[bot] via Test Image / Grype #11476
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file python uv

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant