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

[mergify]

⏳ The pull request #344 is embarked for merge and currently being checked. ⏳

Branch main (a4ccdc8), #348, #337 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]
  • chore(deps): update python to >=3.14.5,<3.15 #344
• check-success = Check Dependency Compatibility
  • chore(deps): update python to >=3.14.5,<3.15 #344
• files ~= ^(uv.lock|pyproject.toml)$
  • chore(deps): update python to >=3.14.5,<3.15 #344
• any of [🛡 GitHub repository ruleset rule main]:
  • check-neutral = Mergify Merge Protections
    • chore(deps): update python to >=3.14.5,<3.15 #344
  • check-skipped = Mergify Merge Protections
    • chore(deps): update python to >=3.14.5,<3.15 #344
  • check-success = Mergify Merge Protections
    • chore(deps): update python to >=3.14.5,<3.15 #344

---
checking_base_sha: cb26379a1eb57ab309e6938e1e0253706b7db11a
previous_failed_batches: []
pull_requests:
  - number: 344
    scopes: []
scopes: []
...

[warestack]

🛡️ Warestack Governance Checks

No governance rules are configured for this repository yet.

Warestack lets your team define, enforce, and audit engineering standards directly on GitHub Pull Requests — without leaving your workflow.

Get started in 2 minutes:

1. Claim your Warestack profile to activate governance for MH0386/MH0386.github.io
2. Configure rules for PR quality, CI requirements, commit conventions, and more
3. Receive automated feedback on every PR

---

This message will disappear once your installation is linked to a Warestack account. It will not be posted again on future PRs once you've claimed your profile.

[deepsource-io]

DeepSource Code Review

We reviewed changes in a4ccdc8...371d6f8 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 16, 2026 11:34p.m.	Review ↗
Secrets		Apr 16, 2026 11:34p.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]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates Python version compatibility and development tooling versions, with corresponding dependency lockfile adjustments for the Renovate-managed dependency bump.

Flow diagram for updated Python and dev dependency constraints

flowchart TD
  A[Project_configuration_pyproject_toml] --> B[Runtime_requirement_requires_python_3_14_4_to_3_15]
  A --> C[Runtime_dependency_reflex_min_0_8_28_post1]
  A --> D[Dev_dependency_group_dev]
  D --> E[ruff_min_0_15_10]
  D --> F[ty_min_0_0_28]
  B --> G[Developer_environment_must_use_Python_3_14_4_or_newer_but_less_than_3_15]
  E --> H[Code_quality_checks_use_newer_ruff_version]
  C --> I[Application_runtime_depends_on_reflex]

Loading

File-Level Changes

Change	Details	Files
Relaxed minimum supported Python patch version and bumped development linting dependency, updating the lockfile accordingly.	Raised the minimum required Python version from 3.14.3 to 3.14.4 while keeping the upper bound unchanged. Increased the minimum ruff development dependency version from 0.15.9 to 0.15.10. Regenerated the dependency lockfile to reflect the updated Python and ruff versions.	pyproject.toml uv.lock

---

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

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud