Skip to content

merge queue: checking #1380 on master (b0237fa) - #1385

Closed
mergify[bot] wants to merge 3 commits into
masterfrom
mergify/merge-queue/6787b956c3
Closed

merge queue: checking #1380 on master (b0237fa)#1385
mergify[bot] wants to merge 3 commits into
masterfrom
mergify/merge-queue/6787b956c3

Conversation

@mergify

@mergify mergify Bot commented Oct 16, 2026 •
edited
Loading

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 oval-rosette-2oxa4n of the changes queue, to test #1380 before it merges into master. Pushing to this branch or closing this pull request removes #1380 from the queue.

What this draft tests

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

  1. master at b0237fa
  2. #1380, the pull request of this batch

🎉 Where it stands: checks passed

CI passed on this draft.

Follow the changes queue in the dashboard

What happens next

  • Mergify merges #1380 into master and closes this draft.
Metadata for CI tooling, read by mergify ci 
---
all_scopes: false
checking_base_sha: b0237fa0096286c78e8f684c450b6c981816004e
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 1380
    scopes:
      - core
scopes:
  - core
...
1 scope
  • core
Required conditions of queue rule changes 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/NAPI Build (Linux ARM64 GNU)
    • check-neutral = @github-actions/NAPI Build (Linux ARM64 GNU)
    • check-skipped = @github-actions/NAPI Build (Linux ARM64 GNU)
  • any of [🛡 GitHub repository ruleset rule master]:
    • check-success = @github-actions/NAPI Build (Windows)
    • check-neutral = @github-actions/NAPI Build (Windows)
    • check-skipped = @github-actions/NAPI Build (Windows)
  • 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/JS Test (Windows)
    • check-neutral = @github-actions/JS Test (Windows)
    • check-skipped = @github-actions/JS Test (Windows)
  • 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
Required conditions to stay in the queue
Queue graph

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

graph LR
    b9edf93b52144759a002d6589af489a0["oval-rosette-2oxa4n<br/>#1380<br/>scopes: core"]
    b9c1269347574d1c9dafa1df567c0969["interior-pate-fzbynp<br/>#1381<br/>scopes: core"]
    b9edf93b52144759a002d6589af489a0 --> b9c1269347574d1c9dafa1df567c0969
    style b9edf93b52144759a002d6589af489a0 fill:#6366f1,color:#fff
Loading

tignear and others added 3 commits October 17, 2026 07:25
@tignear
chore(deps): update wasmtime to 49.0.3 and cranelift to 0.136.3
92a005e 
wasmtime 49.0.2 is affected by twelve RustSec advisories (RUSTSEC-2026-0353
and others) fixed in 49.0.3. cranelift-jit 0.136.2 pins the matching
wasmtime-internal crates, so both move together. chacha20 0.10.1 was yanked.
@tignear
ci: check dependencies with cargo-deny
a8d247c 
Add deny.toml covering advisories, licenses, bans and sources, a workflow
that runs it on dependency changes and daily, and cargo-deny in the dev shell.
@mergify @mergify-commit-signer
Merge of #1380
547e928
@mergify mergify Bot mentioned this pull request Oct 16, 2026
Merged
@mergify mergify Bot closed this Oct 16, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/6787b956c3 branch October 16, 2026 23:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@tignear