merge queue: checking #228 on main (c580165), stacked on #230 and #229

[mergify]

Note

This is a merge queue draft opened by Mergify. Nobody needs to act on it.
Mergify opened it for batch pleased-navarin-77x2oa of the default queue, to test #228 before it merges into main. Pushing to this branch or closing this pull request removes #228 from the queue.

What this draft tests

Mergify checks that #228 still passes CI once combined with everything queued ahead of it. CI runs on this draft's code, built in this order:

1. main at c580165
2. the 2 pull requests queued ahead of this batch, listed below, which bring the tip to d7458f2
3. #228, the pull request of this batch

The check is speculative: it assumes the pull requests ahead will merge, so it starts without waiting for them.

🎉 Where it stands: checks passed

CI passed on this draft.

Follow the default queue in the dashboard

What happens next

• Once the pull requests ahead have merged, Mergify merges #228 into main and closes this draft.
• If a pull request ahead fails or leaves the queue without merging, this batch is requeued and checked again on a new draft: these checks assumed it would merge.

Tip

A red check is not necessarily caused by this batch. These checks run on a tip that also carries the commits of the 2 pull requests ahead, so a failure here can come from them as much as from #228. See only this batch's changes.

Queued ahead of this batch

These pull requests entered the queue before this batch and are not part of it.

• #230
• #229

Metadata for CI tooling, read by mergify ci

---
all_scopes: false
checking_base_sha: d7458f2fc2e234d83ff55d749088b3d835256209
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 228
    scopes: []
scopes: []
...

Required conditions of queue rule default for merge

No extra conditions.

Required conditions to stay in the queue

None

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This merge-queue draft updates pinned GitHub Actions revisions, upgrades the Android Gradle wrapper from 9.8.0 to 9.8.1 with a new checksum, and refreshes the uv lockfile; review should focus on action provenance/version comments, Gradle compatibility, checksum correctness, and whether the lockfile changes are limited to the intended updates.

File-Level Changes

Change	Details	Files
Refresh pinned GitHub Actions dependencies used by build, development setup, mobile, and release workflows.	Update the pinned setup-uv revision in build and Copilot setup workflows. Update pinned upload-artifact and download-artifact revisions while retaining their existing major versions. Verify that action version comments remain accurate, including the setup-uv comment change in the Copilot workflow.	.github/workflows/build.yml .github/workflows/copilot-setup-steps.yml .github/workflows/mobile.yml .github/workflows/release.yml
Upgrade the Android build toolchain to Gradle 9.8.1 with a matching integrity checksum.	Change the Gradle distribution URL from 9.8.0 to 9.8.1. Replace the wrapper SHA-256 checksum for the new distribution.	mobile/gradle/wrapper/gradle-wrapper.properties
Regenerate the Python dependency lockfile to reflect the queued dependency/tooling updates.	Review the 19 added and 19 removed lockfile entries for intended package and resolution changes.	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.

[kanarek-companion]

🐤 Kanarek · ⚫ closed

branch ⚫

This branch has left the building. Nothing further to peck at.

_{Kanarek, Mobile, Repo root · 7 files}