Skip to content

merge queue: checking #1291 on master (3aa303e), stacked on #1337 - #1344

Closed
mergify[bot] wants to merge 10 commits into
masterfrom
mergify/merge-queue/1f169dabb9
Closed

merge queue: checking #1291 on master (3aa303e), stacked on #1337#1344
mergify[bot] wants to merge 10 commits into
masterfrom
mergify/merge-queue/1f169dabb9

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 red-eclair-db3g3f of the changes queue, to test #1291 before it merges into master. Pushing to this branch or closing this pull request removes #1291 from the queue.

What this draft tests

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

  1. master at 3aa303e
  2. the pull request queued ahead of this batch, listed below, which brings the tip to ba3d7c6
  3. #1291, 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: being checked

CI is running on this draft.

Waiting for

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

Follow the changes queue in the dashboard

What happens next

  • Once the checks pass, every merge condition is met and the pull requests ahead have merged, Mergify merges #1291 into master and closes this draft.
  • If a check fails, Mergify removes #1291 from the queue and closes this draft.
  • If the checks have not finished after 3 hours (checks_timeout), Mergify removes #1291 from the queue 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 pull request ahead, so a failure here can come from it as much as from #1291. See only this batch's changes.

Queued ahead of this batch

This pull request entered the queue before this batch and is not part of it.

  • #1337 — shares the scope core
Metadata for CI tooling, read by mergify ci 
---
all_scopes: false
checking_base_sha: ba3d7c6aa959b31a37d7c61715aff2f795602722
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 1291
    scopes:
      - core
scopes:
  - core
...
1 scope
  • core
Required conditions of queue rule changes for merge
  • check-success = Queue validation
  • any of [🛡 GitHub repository ruleset rule master]:
    • check-neutral = @github-actions/Rust Test & NAPI Build
    • check-skipped = @github-actions/Rust Test & NAPI Build
    • check-success = @github-actions/Rust Test & NAPI Build
  • any of [🛡 GitHub repository ruleset rule master]:
    • check-neutral = @github-actions/JS Test (Windows)
    • check-skipped = @github-actions/JS Test (Windows)
    • check-success = @github-actions/JS Test (Windows)
  • check-success = Conventional Commit title
  • 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/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
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
    d00786f1f8a24e71b9597f532749dbb1["vital-roux-lvu2mr<br/>#1337<br/>scopes: core"]
    0c3b9449f88a4c16b969b7a85fa52d81["red-eclair-db3g3f<br/>#1291<br/>scopes: core"]
    d00786f1f8a24e71b9597f532749dbb1 --> 0c3b9449f88a4c16b969b7a85fa52d81
    style 0c3b9449f88a4c16b969b7a85fa52d81 fill:#6366f1,color:#fff
Loading

tignear and others added 10 commits October 16, 2026 17:14
@tignear
ci: run Veryl proof gates only weekly or manually
bb57cc1
@tignear
chore(lydite): remove unreferenced audit evidence and examples
378c9d8 
Drop archived publication/validation records, old measurement results,
and scripts and fixtures that no CI step, test, or live script reads.
The history remains in tignear/hwverify.
@tignear
docs(lydite): translate README to English and trim it
a9eb32d 
Fold repeated caveats into the trust-boundary pointer and drop the
synthesis row that linked outside this repository.
@tignear
docs(lydite): translate the remaining docs to English
1f01e36 
Translate specifications, scoped specifications, expectations, language,
models and program contracts, and rename proof/README-ja.md to
proof/README.md. Code blocks and existing English sections are unchanged.
@tignear
ci(lydite): sync Veryl conformance lockfile with syn 3.0.8
60fd737
@tignear
ci(renovate): stop updating the Veryl conformance workspace
8fcfd65 
Renovate cannot update its Cargo.lock because the workspace lists the
generated-suite member that run_ci.sh creates, so each manifest bump
broke the --locked veryl-fv build.
@tignear
chore(lydite): keep the evidence and checks that are still referenced
096831a 
Restore the archive validation record, the negative SDC probe, the
structural-solver campaign runners and the control-invariant regression,
run that regression in the RV32I gate, and keep a generator for the live
auto_array_sum fixture.
@tignear
test(lydite): add the new sparse-commit case to the corpus golden
52a6d1a 
Master added nba_dynamic_array::test_sparse_commit_reaches_every_summary_word;
the corpus gate verifies its reads, so record it in the reviewed manifest.
@mergify @mergify-commit-signer
Merge of #1337
ba3d7c6
@mergify @mergify-commit-signer
Merge of #1291
89c0e23
@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/1f169dabb9 branch October 16, 2026 09:43
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