[mergify]

Note

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

What this draft tests

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

1. main at 2f494d2
2. #240, 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 #240 into main and closes this draft.

Metadata for CI tooling, read by mergify ci

---
all_scopes: false
checking_base_sha: 2f494d21cccd68a9944588995650c0f33408bb65
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 240
    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 validates PR #240 on top of main; its effective changes update the commit pins for actions/upload-artifact and actions/setup-node in CI workflows, with no changes to workflow configuration, inputs, or execution logic.

File-Level Changes

Change	Details	Files
Refresh pinned GitHub Actions revisions while retaining the existing major versions and workflow behavior.	Update all artifact-upload steps to a new immutable actions/upload-artifact commit. Update the backend Node.js setup step to a new immutable actions/setup-node commit. Apply the artifact action refresh across Android, MegaLinter, and shared iOS workflows without changing inputs or conditions.	.github/workflows/android-ci.yml .github/workflows/backend-ci.yml .github/workflows/mega-linter.yml .github/workflows/shared-ios-ci.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

• 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.

[github-actions]

✅MegaLinter analysis: Success

Descriptor	Linter	Files	Fixed	Errors	Max errors	Warnings	Elapsed time
✅ ACTION	actionlint	4		0		0	0.51s
✅ ACTION	zizmor	4	2	0		0	0.46s
✅ YAML	prettier	4	2	0		0	0.33s
✅ YAML	v8r	4		0		0	2.13s
✅ YAML	yamllint	4		0		0	0.9s

See detailed reports in MegaLinter artifacts
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff

MegaLinter is provided by OX Security
Show us your support by starring ⭐ the repository

[kanarek-companion]

🐤 Kanarek · ⚫ closed

branch ⚫

航班取消。金丝雀关灯收摊，今天就到这里。

_{Kanarek · 4 files}