Skip to content

chore: promote staging to staging-promote/eb3fa0e6-23858863254 (2026-04-01 18:14 UTC) - #1885

Merged
henrypark133 merged 8 commits into
staging-promote/eb3fa0e6-23858863254from
staging-promote/510fe19a-23863770631
Apr 1, 2026
Merged

henrypark133 merged 8 commits into
staging-promote/eb3fa0e6-23858863254from
staging-promote/510fe19a-23863770631

Conversation

@ironclaw-ci

@ironclaw-ci ironclaw-ci Bot commented Apr 1, 2026 •

Copy link
Copy Markdown
Contributor

Auto-promotion from staging CI

Batch range: eb3fa0e64cf51982b8ab1a06f3fdd9969867b2bf..510fe19a06b75455fa74de65a50bbfb23402697f
Promotion branch: staging-promote/510fe19a-23863770631
Base: staging-promote/eb3fa0e6-23858863254
Triggered by: Staging CI batch at 2026-04-01 18:14 UTC

Commits in this batch (1):

Current commits in this promotion (0)

Current base: staging-promote/eb3fa0e6-23858863254
Current head: staging-promote/510fe19a-23863770631
Current range: origin/staging-promote/eb3fa0e6-23858863254..origin/staging-promote/510fe19a-23863770631

  • (no non-merge commits in range)

Auto-updated by staging promotion metadata workflow

Waiting for gates:

  • Tests: pending
  • E2E: pending
  • Claude Code review: pending (will post comments on this PR)

Auto-created by staging-ci workflow

…#1848)

For channel mentions, the relay channel used event.channel_id (e.g.
"C088K6C3SQZ") as the thread_id fallback. Slack requires thread_ts to
be a message timestamp, so it silently ignored this and posted a
top-level message instead of threading.

Now uses event.id (the Slack message ts, e.g. "1609459200.000100") as
the fallback, so responses are always threaded under the user's message.
Also fixes metadata["thread_id"] to use the same value.

Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@github-actions github-actions Bot added size: M 50-199 changed lines risk: medium Business logic, config, or moderate-risk modules contributor: core 20+ merged PRs labels Apr 1, 2026
* test(routines): add issue 1781 coverage

* fix: address PR review feedback
* test(e2e): cover chat approval parity across channels

* fix: harden chat approval prompt rendering
* Expand GitHub WASM tool surface

* Tighten GitHub tool input validation
* test(e2e): add agent loop recovery coverage

* test(e2e): harden mock message text parsing
…5626

chore: promote staging to staging-promote/2f2ad260-23866616993 (2026-04-01 22:10 UTC)
…6993

chore: promote staging to staging-promote/510fe19a-23863770631 (2026-04-01 19:23 UTC)
@github-actions github-actions Bot added scope: agent Agent core (agent loop, router, scheduler) scope: channel Channel infrastructure scope: channel/wasm WASM channel runtime scope: tool Tool infrastructure scope: tool/wasm WASM tool sandbox scope: ci CI/CD workflows scope: docs Documentation labels Apr 1, 2026
@henrypark133
henrypark133 merged commit 38e0165 into staging-promote/eb3fa0e6-23858863254 Apr 1, 2026
13 checks passed
@github-actions github-actions Bot added size: XL 500+ changed lines and removed size: M 50-199 changed lines labels Apr 1, 2026
@henrypark133
henrypark133 deleted the staging-promote/510fe19a-23863770631 branch April 1, 2026 22:33
theredspoon pushed a commit to theredspoon/ironclaw that referenced this pull request Jun 21, 2026
…3863770631

chore: promote staging to staging-promote/e274b28b-23858863254 (2026-04-01 18:14 UTC)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

contributor: core 20+ merged PRs risk: medium Business logic, config, or moderate-risk modules scope: agent Agent core (agent loop, router, scheduler) scope: channel/wasm WASM channel runtime scope: channel Channel infrastructure scope: ci CI/CD workflows scope: docs Documentation scope: tool/wasm WASM tool sandbox scope: tool Tool infrastructure size: XL 500+ changed lines staging-promotion

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants