[mergify]

Note

This is a merge queue draft opened by Mergify. Nobody needs to act on it.
Mergify opened it for batch promising-painsport-tlzsln of the dependencies queue, to test #2413 before it merges into master. Pushing to this branch or closing this pull request removes #2413 from the queue.

What this draft tests

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

1. master at a037246
2. #2413, the pull request of this batch

🎉 Where it stands: checks passed

CI passed on this draft.

Follow the dependencies queue in the dashboard

What happens next

• Mergify merges #2413 into master and closes this draft.

Metadata for CI tooling, read by mergify ci

---
all_scopes: false
checking_base_sha: a037246f79080d37487d12de591e90e9e3923711
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 2413
    scopes:
      - core
scopes:
  - core
...

1 scope

• core

Required conditions of queue rule dependencies for merge

• check-success = Conventional Commit title
• check-success = Queue validation
• any of [🛡 GitHub repository ruleset rule master]:
  • check-success = @github-actions/Lint & Format
  • check-neutral = @github-actions/Lint & Format
  • check-skipped = @github-actions/Lint & Format
• any of [🛡 GitHub repository ruleset rule master]:
  • check-success = @github-actions/Rust Test & NAPI Build
  • check-neutral = @github-actions/Rust Test & NAPI Build
  • check-skipped = @github-actions/Rust Test & NAPI Build
• any of [🛡 GitHub repository ruleset rule master]:
  • check-success = @github-actions/JS Test (Ubuntu)
  • check-neutral = @github-actions/JS Test (Ubuntu)
  • check-skipped = @github-actions/JS Test (Ubuntu)
• any of [🛡 GitHub repository ruleset rule master]:
  • check-success = @github-actions/Conventional Commit title
  • check-neutral = @github-actions/Conventional Commit title
  • check-skipped = @github-actions/Conventional Commit title
• any of [🛡 GitHub repository ruleset rule master]:
  • check-success = @github-actions/Queue validation
  • check-neutral = @github-actions/Queue validation
  • check-skipped = @github-actions/Queue validation

Required conditions to stay in the queue

• -conflict
  • chore(deps): update rust toolchain to 19ecdd0 #2413
• -draft
  • chore(deps): update rust toolchain to 19ecdd0 #2413
• -head ~= ^(integration/|renovate/veryl-crates$|upgrade/veryl-|release-please--branches--master--components--celox$|master$)
  • chore(deps): update rust toolchain to 19ecdd0 #2413
• -label = release:hold
  • chore(deps): update rust toolchain to 19ecdd0 #2413
• base ~= ^(master|develop)$
  • chore(deps): update rust toolchain to 19ecdd0 #2413
• head ~= ^renovate/
  • chore(deps): update rust toolchain to 19ecdd0 #2413
• any of:
  • head != release-please--branches--master--components--celox
    • chore(deps): update rust toolchain to 19ecdd0 #2413
  • label = merge-ready
    • chore(deps): update rust toolchain to 19ecdd0 #2413
• any of [🛡 GitHub repository ruleset rule master]:
  • check-success = @github-actions/Lint & Format
    • chore(deps): update rust toolchain to 19ecdd0 #2413
  • check-neutral = @github-actions/Lint & Format
    • chore(deps): update rust toolchain to 19ecdd0 #2413
  • check-skipped = @github-actions/Lint & Format
    • chore(deps): update rust toolchain to 19ecdd0 #2413
• any of [🛡 GitHub repository ruleset rule master]:
  • check-success = @github-actions/Rust Test & NAPI Build
    • chore(deps): update rust toolchain to 19ecdd0 #2413
  • check-neutral = @github-actions/Rust Test & NAPI Build
    • chore(deps): update rust toolchain to 19ecdd0 #2413
  • check-skipped = @github-actions/Rust Test & NAPI Build
    • chore(deps): update rust toolchain to 19ecdd0 #2413
• any of [🛡 GitHub repository ruleset rule master]:
  • check-success = @github-actions/JS Test (Ubuntu)
    • chore(deps): update rust toolchain to 19ecdd0 #2413
  • check-neutral = @github-actions/JS Test (Ubuntu)
    • chore(deps): update rust toolchain to 19ecdd0 #2413
  • check-skipped = @github-actions/JS Test (Ubuntu)
    • chore(deps): update rust toolchain to 19ecdd0 #2413
• any of [🛡 GitHub repository ruleset rule master]:
  • check-success = @github-actions/Conventional Commit title
    • chore(deps): update rust toolchain to 19ecdd0 #2413
  • check-neutral = @github-actions/Conventional Commit title
    • chore(deps): update rust toolchain to 19ecdd0 #2413
  • check-skipped = @github-actions/Conventional Commit title
    • chore(deps): update rust toolchain to 19ecdd0 #2413
• any of [🛡 GitHub repository ruleset rule master]:
  • check-skipped = @github-actions/Queue validation
    • chore(deps): update rust toolchain to 19ecdd0 #2413
  • check-neutral = @github-actions/Queue validation
    • chore(deps): update rust toolchain to 19ecdd0 #2413
  • check-success = @github-actions/Queue validation
    • chore(deps): update rust toolchain to 19ecdd0 #2413

Queue graph

The diagram is not laid out in queue order, so a node's position says nothing about when it merges.

graph LR
    f5bd0169a4394479b4fd0a71298a72a6["promising-painsport-tlzsln<br/>#2413<br/>scopes: core"]
    46d39c7ca3204d5fa650b0f5106bbc8f["minor-cantal-552olw<br/>#2408<br/>scopes: core"]
    f5bd0169a4394479b4fd0a71298a72a6 --> 46d39c7ca3204d5fa650b0f5106bbc8f
    style f5bd0169a4394479b4fd0a71298a72a6 fill:#6366f1,color:#fff

Loading