Skip to content

merge queue: checking #230 on main (c580165) - #231

Closed
mergify[bot] wants to merge 2 commits into
mainfrom
mergify/merge-queue/1e6ecfbd17
Closed

mergify[bot] wants to merge 2 commits into
mainfrom
mergify/merge-queue/1e6ecfbd17

Conversation

@mergify

@mergify mergify Bot commented Oct 16, 2026 •

Copy link
Copy Markdown
Contributor

Note

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

What this draft tests

Mergify checks that #230 still passes CI on top of main. CI runs on this draft's code, built in this order:

  1. main at c580165
  2. #230, the pull request of this batch

🎉 Where it stands: checks passed

CI passed on this draft.

Follow the default queue in the dashboard

What happens next

  • Mergify merges #230 into main and closes this draft.
Metadata for CI tooling, read by mergify ci
---
all_scopes: false
checking_base_sha: c580165634a3b7de8e8a0983ed0941cb372d8ea1
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 230
    scopes: []
scopes: []
...
Required conditions of queue rule default for merge

No extra conditions.

Required conditions to stay in the queue

None

dependabot Bot and others added 2 commits October 15, 2026 19:43
Bumps the actions group with 3 updates: [astral-sh/setup-uv](https://github.com/astral-sh/setup-uv), [actions/upload-artifact](https://github.com/actions/upload-artifact) and [actions/download-artifact](https://github.com/actions/download-artifact).


Updates `astral-sh/setup-uv` from 10.2.0 to 10.3.0
- [Release notes](https://github.com/astral-sh/setup-uv/releases)
- [Commits](astral-sh/setup-uv@c18668a...1c37ad0)

Updates `actions/upload-artifact` from 7.0.1 to 7.0.2
- [Release notes](https://github.com/actions/upload-artifact/releases)
- [Commits](actions/upload-artifact@043fb46...cf430e0)

Updates `actions/download-artifact` from 8.0.1 to 8.0.2
- [Release notes](https://github.com/actions/download-artifact/releases)
- [Commits](actions/download-artifact@3e5f45b...9000827)

---
updated-dependencies:
- dependency-name: astral-sh/setup-uv
  dependency-version: 10.3.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: actions
- dependency-name: actions/upload-artifact
  dependency-version: 7.0.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: actions
- dependency-name: actions/download-artifact
  dependency-version: 8.0.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: actions
...

Signed-off-by: dependabot[bot] <support@github.com>
@sourcery-ai

sourcery-ai Bot commented Oct 16, 2026

Copy link
Copy Markdown
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This merge-queue draft validates PR #230 on top of main; the only included implementation changes refresh pinned setup-uv, upload-artifact, and download-artifact GitHub Actions revisions across the CI, development, mobile, and release workflows without changing their inputs or execution logic.

File-Level Changes

Change Details Files
Refresh pinned GitHub Actions dependencies to newer immutable commits while retaining the existing workflow behavior.
  • Update the pinned setup-uv revision in the build workflow.
  • Update the pinned setup-uv revision and version annotation in the Copilot setup workflow.
  • Update upload-artifact pins used by build and mobile workflows.
  • Update download-artifact pins used by the release workflow.
.github/workflows/build.yml
.github/workflows/copilot-setup-steps.yml
.github/workflows/mobile.yml
.github/workflows/release.yml

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

@mergify mergify Bot closed this Oct 16, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/1e6ecfbd17 branch October 16, 2026 04:32
@kanarek-companion

Copy link
Copy Markdown

🐤 Kanarek · ⚫ closed

branch ⚫

PR 已关闭。金丝雀扫走面包屑,笼子恢复待机。

Kanarek · 4 files

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