chore: promote staging to staging-promote/4c043bf0-23573031775 (2026-03-26 07:26 UTC)#1668
Merged
henrypark133 merged 66 commits intostaging-promote/4c043bf0-23573031775from Mar 26, 2026
Conversation
…3042 chore: promote staging to staging-promote/ec04354c-23271447493 (2026-03-19 00:12 UTC)
…6242 chore: promote staging to staging-promote/b9e5acf6-23283208580 (2026-03-19 15:15 UTC)
…8580 chore: promote staging to staging-promote/3dcccc1e-23280048384 (2026-03-19 06:44 UTC)
…8384 chore: promote staging to staging-promote/ec04354c-23271447493 (2026-03-19 04:37 UTC)
…6661 chore: promote staging to staging-promote/ec04354c-23271447493 (2026-03-19 16:48 UTC)
…7493 chore: promote staging to main (2026-03-18 23:07 UTC)
Co-authored-by: ironclaw-ci[bot] <266877842+ironclaw-ci[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
…4063 chore: promote staging to staging-promote/65062f3c-23317058602 (2026-03-19 23:06 UTC)
…8602 chore: promote staging to staging-promote/52ca9d65-23312673755 (2026-03-19 21:10 UTC)
…3755 chore: promote staging to staging-promote/71f41dd1-23309993684 (2026-03-19 19:18 UTC)
…3684 chore: promote staging to staging-promote/71f9012d-23307625134 (2026-03-19 18:14 UTC)
…5134 chore: promote staging to staging-promote/ec04354c-23271447493 (2026-03-19 17:20 UTC)
Co-authored-by: ironclaw-ci[bot] <266877842+ironclaw-ci[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
…2672 chore: promote staging to staging-promote/c4ab3825-23321164063 (2026-03-20 02:56 UTC)
…7636 chore: promote staging to staging-promote/cba1bc37-23334371795 (2026-03-20 16:12 UTC)
…1795 chore: promote staging to staging-promote/c1762616-23332963145 (2026-03-20 08:09 UTC)
…3145 chore: promote staging to staging-promote/b952d229-23331469361 (2026-03-20 07:18 UTC)
…9361 chore: promote staging to staging-promote/806d4028-23330265305 (2026-03-20 06:16 UTC)
…5305 chore: promote staging to staging-promote/455f543b-23329172268 (2026-03-20 05:23 UTC)
…2351 chore: promote staging to staging-promote/3da9810e-23351687636 (2026-03-20 17:14 UTC)
…1011 chore: promote staging to staging-promote/ee6f5cd6-23354122351 (2026-03-20 19:41 UTC)
…3131 chore: promote staging to staging-promote/ab0ad948-23563320113 (2026-03-25 21:37 UTC)
…0113 chore: promote staging to staging-promote/c949521d-23562109203 (2026-03-25 20:47 UTC)
…9203 chore: promote staging to staging-promote/0341fcc9-23558273569 (2026-03-25 20:19 UTC)
…3569 chore: promote staging to staging-promote/6daa2f15-23538193544 (2026-03-25 18:47 UTC)
…3544 chore: promote staging to staging-promote/82822d7b-23516534944 (2026-03-25 12:01 UTC)
…2268 chore: promote staging to staging-promote/89203225-23327092672 (2026-03-20 04:32 UTC)
Co-authored-by: ironclaw-ci[bot] <266877842+ironclaw-ci[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
* fix(llm): filter XML tool-call recovery by context * fix: address review comments on PR #1641
Code reviewFound 3 issues:
Positive observations: Comprehensive test coverage, correct filtering of tool calls from code regions, no .unwrap() in production code. |
This was referenced Mar 26, 2026
Closed
Chore: Sync Main/Staging
…2140 chore: promote staging to staging-promote/ed4d9293-23582522167 (2026-03-26 18:18 UTC)
…override (#1681) * fix(extensions): channel-relay auth dead-end, add observability and relay URL override Fix a bug where clicking Activate on the Slack relay extension produces a dead-end "Authentication required" error with no OAuth URL. The root cause: `auth_channel_relay()` used `is_relay_channel()` to check auth status, but that function returns true as soon as the extension is *installed* (in-memory set), before OAuth completes. This short-circuits the OAuth flow so the authorization URL is never offered. Changes: 1. **Bug fix** — `auth_channel_relay()` now uses `has_stored_team_id()` which only checks the persistent settings store for an actual team_id. The extension list `authenticated` field uses the same check so the UI accurately reflects OAuth completion status. 2. **Observability** — Added debug/warn/info tracing to all channel-relay code paths that were previously silent on failure: - `activate_channel_relay`: team_id retrieval, relay config, signing secret fetch, hot_add, cache operations - `auth_channel_relay`: auth check, OAuth initiation, nonce storage - `extensions_activate_handler`: request entry, auth fallback flow - `slack_relay_oauth_callback_handler`: team_id persistence (was silently ignored with `let _`) - `RelayClient`: initiate_oauth, get_signing_secret, proxy_provider all log URL, status, and errors - `has_stored_team_id`: store read success/failure 3. **Per-extension relay URL override** — Users can now override the CHANNEL_RELAY_URL via Settings > Extensions > Reconfigure. Stored under `extensions.{name}.relay_url` in settings. Both auth and activate read this override before falling back to the env default. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * style: cargo fmt Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * fix: address review feedback — clear relay_url override and improve log message 1. Allow clearing the relay_url override: when an optional setup field with a setting_path is submitted empty, delete the stored setting so the system reverts to the env/default value. Previously empty values were silently skipped, making it impossible to undo an override from the UI. 2. Improve the OAuth callback team_id persistence error log to be self-contained without referencing implementation details. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * style: collapse nested if per clippy::collapsible_if Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * fix: address review feedback — security, scope consistency, and error handling 1. OAuth callback team_id persistence is now fatal: if set_setting fails, the callback returns an error instead of proceeding to activate (which would re-read from the store and fail anyway). 2. effective_relay_url uses owner scope (self.user_id) for reads, matching configure() which writes under the same scope. Prevents multi-user mismatch where an override saved via Reconfigure was invisible during auth/activation. 3. has_stored_team_id uses owner scope for the same reason — the OAuth callback stores team_id under state.owner_id (= self.user_id). 4. Security: effective_relay_url validates the override URL — only http/https without embedded credentials (userinfo) is accepted. This prevents API-key exfiltration if a user points relay_url at an attacker-controlled host. Logs only host portion, not full URL. 5. Fixed effective_relay_url docstring to match behavior (returns Option, callers handle the fallback). 6. get_setup_schema for ChannelRelay now logs a warning on settings store errors instead of silently returning None. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…1675 chore: promote staging to staging-promote/ed4d9293-23582522167 (2026-03-26 21:08 UTC)
00aba92
into
staging-promote/4c043bf0-23573031775
13 checks passed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Auto-promotion from staging CI
Batch range:
4c043bf05767d7e1ab74552eb010182ec44b3222..ed4d92932ac5d2d9123a8448aac4627bb8bb2d7cPromotion branch:
staging-promote/ed4d9293-23582522167Base:
staging-promote/4c043bf0-23573031775Triggered by: Staging CI batch at 2026-03-26 07:26 UTC
Commits in this batch (2):
Current commits in this promotion (14)
Current base:
staging-promote/4c043bf0-23573031775Current head:
staging-promote/ed4d9293-23582522167Current range:
origin/staging-promote/4c043bf0-23573031775..origin/staging-promote/ed4d9293-23582522167Auto-updated by staging promotion metadata workflow
Waiting for gates:
Auto-created by staging-ci workflow