Skip to content

merge queue: embarking main (a4ccdc8), #348, #349, #337, #342 and #344 together#367

Closed
mergify[bot] wants to merge 11 commits intomainfrom
mergify/merge-queue/dfd7a55c28
Closed

merge queue: embarking main (a4ccdc8), #348, #349, #337, #342 and #344 together#367
mergify[bot] wants to merge 11 commits intomainfrom
mergify/merge-queue/dfd7a55c28

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify Bot commented Apr 9, 2026

✨ Pull request #342 which was ahead in the queue has been dequeued (for the following reason: pull request manually updated). The pull request #344 has been re-embarked. ✨

Branch main (a4ccdc8), #348, #349, #337, #342 and #344 are embarked together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of #344.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue rule Python Dependency Updates for merge:

  • check-success = Test Image / API Test
  • any of [🛡 GitHub repository ruleset rule main]:
    • check-neutral = Mergify Merge Protections
    • check-skipped = Mergify Merge Protections
    • check-success = Mergify Merge Protections

Required conditions to stay in the queue:

  • author = renovate[bot]
  • check-success = Check Dependency Compatibility
  • files ~= ^(uv.lock|pyproject.toml)$
  • any of [🛡 GitHub repository ruleset rule main]:
    • check-neutral = Mergify Merge Protections
    • check-skipped = Mergify Merge Protections
    • check-success = Mergify Merge Protections
---
checking_base_sha: 6121ce26c3f3702b51955326f90f972bcc0896d0
previous_failed_batches: []
pull_requests:
  - number: 344
    scopes: []
scopes: []
...

@deepsource-io
Copy link
Copy Markdown

deepsource-io Bot commented Apr 9, 2026

DeepSource Code Review

We reviewed changes in a4ccdc8...e3e7086 on this pull request. Below is the summary for the review, and you can see the individual issues we found as inline review comments.

See full review on DeepSource ↗

PR Report Card

Overall Grade   Security  

Reliability  

Complexity  

Hygiene  

Code Review Summary

Analyzer Status Updated (UTC) Details
Python Apr 9, 2026 9:17p.m. Review ↗
Secrets Apr 9, 2026 9:17p.m. Review ↗

Important

AI Review is run only on demand for your team. We're only showing results of static analysis review right now. To trigger AI Review, comment @deepsourcebot review on this thread.

@sourcery-ai
Copy link
Copy Markdown
Contributor

sourcery-ai Bot commented Apr 9, 2026

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates Python toolchain and linting-related dependencies (ruff, uv, Python version requirement) and refreshes the uv lockfile to align with these versions and the existing Reflex dependency.

File-Level Changes

Change Details Files
Bump pre-commit hooks for uv and ruff to newer versions.
  • Update uv-pre-commit hook revision from 0.11.3 to 0.11.6 for uv-sync and uv-lock hooks.
  • Update ruff-pre-commit hook revision from v0.15.9 to v0.15.10 for ruff-check hook.
.pre-commit-config.yaml
Align Python version requirement and dev dependency versions with latest patch-level updates.
  • Increase requires-python from ">=3.14.3,<3.15" to ">=3.14.4,<3.15".
  • Bump ruff dev dependency lower bound from 0.15.9 to 0.15.10 while keeping other dev deps unchanged.
pyproject.toml
Regenerate dependency lockfile to reflect updated Python and tooling versions.
  • Update resolved versions and metadata in uv.lock to remain consistent with the new Python requirement and dependency constraints.
uv.lock

Possibly linked issues

  • #Dependency Dashboard: This merge-queue PR validates and merges the Renovate dependency update PRs referenced in the dependency dashboard.

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud Bot commented Apr 9, 2026

@mergify mergify Bot closed this Apr 16, 2026
@mergify mergify Bot deleted the mergify/merge-queue/dfd7a55c28 branch April 16, 2026 11:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants