Skip to content

merge queue: checking #2430 on master (a3c47fa), stacked on #2425 - #2433

Closed
mergify[bot] wants to merge 4 commits into
masterfrom
mergify/merge-queue/e1938b872e
Closed

merge queue: checking #2430 on master (a3c47fa), stacked on #2425#2433
mergify[bot] wants to merge 4 commits into
masterfrom
mergify/merge-queue/e1938b872e

Conversation

@mergify

@mergify mergify Bot commented Oct 28, 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 ordinary-asperge-1zgt04 of the changes queue, to test #2430 before it merges into master. Pushing to this branch or closing this pull request removes #2430 from the queue.

What this draft tests

Mergify checks that #2430 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 a3c47fa
  2. the pull request queued ahead of this batch, listed below, which brings the tip to 9999e5a
  3. #2430, 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: checks passed

CI passed on this draft.

Follow the changes queue in the dashboard

What happens next

  • Once the pull requests ahead have merged, Mergify merges #2430 into master 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 #2430. 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.

Metadata for CI tooling, read by mergify ci 
---
all_scopes: false
checking_base_sha: 9999e5aed542c3343ea7f1ce947a64e85e536658
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 2430
    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/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

tignear and others added 4 commits October 28, 2026 19:40
@tignear
fix(native): store the mask plane of wide two-state values
c1a0bbf 
On the native x86 and arm64 backends, a store wider than 64 bits into a
4-state variable wrote its mask plane only when the source register had
wide mask chunks. A wide register loaded from a 2-state variable, or
produced by a 2-state operation, has at most a scalar mask, so the
destination kept a stale mask and read back as X or Z.

This showed up in 4-state simulation of a concatenation assignment from a
2-state value wider than 64 bits in a process, `{x, y, z} = w`: the value
is captured in a 4-state temporary and its slices are assigned, so the
targets read 0 (or X for 4-state targets), while Cranelift and wasm gave
the right values. The store now always writes every mask bit: the source's
wide mask chunks when it has them, otherwise its scalar mask for the low
chunk and zero above.

Change-Id: If46d411b2f1bc2e1aa4f99f79033b09df4e11067
@tignear
ci: start the fixer agent from PR mentions
ae54dfb 
A maintainer comment containing @celox-agent on a pull request that targets
develop starts a Claude Managed Agents session for that PR only. The workflow
reacts with eyes, creates the session through the Anthropic API, and replies
with the session ID and Console link, or with the HTTP status and error message
on failure.

The job authenticates to Anthropic through Workload Identity Federation with
the GitHub Actions OIDC token, so no Anthropic API key is stored. The
federation rule accepts only this workflow file on master, run by
issue_comment. The AGENT_GITHUB_TOKEN secret holds the PAT mounted as the
session's repository credential.

Change-Id: I9e01e16c8f0e947da0687fca6b56b63ccbd8bd4a
@mergify @mergify-commit-signer
Merge of #2425
9999e5a
@mergify @mergify-commit-signer
Merge of #2430
b8c3f3e
@mergify mergify Bot mentioned this pull request Oct 28, 2026
Merged
@mergify mergify Bot closed this Oct 28, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/e1938b872e branch October 28, 2026 12:03
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