Skip to content

chore: promote staging to staging-promote/d567d94c-23755250735 (2026-03-30 18:33 UTC) - #1763

Merged
henrypark133 merged 1 commit into
staging-promote/d567d94c-23755250735from
staging-promote/21f613ff-23761172238
Mar 30, 2026
Merged

henrypark133 merged 1 commit into
staging-promote/d567d94c-23755250735from
staging-promote/21f613ff-23761172238

Conversation

@ironclaw-ci

@ironclaw-ci ironclaw-ci Bot commented Mar 30, 2026 •

Copy link
Copy Markdown
Contributor

Auto-promotion from staging CI

Batch range: 2f4eb08613cefff1af8b7b1a475fda00c84dd855..21f613ff2e8a1dc1f809677b3cc669e59ccbddbd
Promotion branch: staging-promote/21f613ff-23761172238
Base: staging-promote/d567d94c-23755250735
Triggered by: Staging CI batch at 2026-03-30 18:33 UTC

Commits in this batch (27):

Current commits in this promotion (1)

Current base: staging-promote/d567d94c-23755250735
Current head: staging-promote/21f613ff-23761172238
Current range: origin/staging-promote/d567d94c-23755250735..origin/staging-promote/21f613ff-23761172238

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

…1762)

* test(e2e): align wasm reinstall expectations with uninstall cleanup

* test(e2e): clarify wasm reinstall fixture semantics
@github-actions github-actions Bot added size: XS < 10 changed lines (excluding docs) risk: low Changes to docs, tests, or low-risk modules contributor: core 20+ merged PRs labels Mar 30, 2026
@claude

claude Bot commented Mar 30, 2026

Copy link
Copy Markdown

Found 1 issue: [LOW:75] Line 426 missing defensive .get() when accessing ext[needs_setup]. The assertion will raise KeyError if missing, while line 428 uses .get() defensively. This is inconsistent error handling in the same test. Summary: This is a test correction aligning expectations with production behavior where ExtensionManager removes secrets on uninstall, so reinstalled extensions start unconfigured. Security is correct. No production code changes needed.

@railway-app
railway-app Bot temporarily deployed to fantastic-reprieve / production March 30, 2026 19:09 Inactive
@henrypark133
henrypark133 merged commit 8be61c2 into staging-promote/d567d94c-23755250735 Mar 30, 2026
43 checks passed
@henrypark133
henrypark133 deleted the staging-promote/21f613ff-23761172238 branch March 30, 2026 19:21
@railway-app
railway-app Bot temporarily deployed to humble-cat / staging-cameron March 30, 2026 20:30 Inactive
drchirag1991 pushed a commit to drchirag1991/ironclaw that referenced this pull request Apr 8, 2026
…3761172238

chore: promote staging to staging-promote/fcc7e8dd-23755250735 (2026-03-30 18:33 UTC)

This branch was previously deployed

4 inactive deployments
humble-cat / staging-cameron — 21f613ff Deployed Mar 30, 2026 by railway-app[bot]
fantastic-reprieve / production — 21f613ff Deployed Mar 30, 2026 by railway-app[bot]
humble-cat / production — 21f613ff Deployed Mar 30, 2026 by railway-app[bot]
pleasing-possibility / production — 21f613ff Deployed Mar 30, 2026 by railway-app[bot]
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: low Changes to docs, tests, or low-risk modules size: XS < 10 changed lines (excluding docs) staging-promotion

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant