Repository navigation
feat(integrations): one Hazel integration, alerts through the bot - #2022
Merged
Merged
Maple Review Bot / Maple / review
succeeded
Oct 31, 2026 in 2m 13s
Confidence 9/10 · No issues found
🟢 Confidence 9/10 · safe to merge. Pure removal of the Hazel OAuth path; it rests on the claim that no stored hazel-oauth destination row exists, which would no longer decode.
no findings · tests covered · risk high −1
Deletes the Hazel OAuth webhook integration so one Hazel connection — the chat connector — covers both chat and alerting, with ?integration=hazel redirecting to chat-hazel. Internally consistent and safe once Hazel #372 ships; the edit to apps/electric-sync/src/shapes/registry.ts is comment-only and does not address the open McpQueryError failures there.
HazelOAuthService, thehazel-oauthdestination type and its transport are gonerouteRedirectsends/integrations?integration=hazeltochat-hazelhazel-oauthdropped from the v2 OpenAPI enum, Google-Chat tests replace the Hazel ones
Before merge
- Manual · Deploy MapleTechLabs/hazel#372 first, or the Hazel channel picker 404s in the destination form
- Manual · Add
channels:readto the Maple bots in both Hazel regions
Production impact
Open errors in the changed files (2)
| Issue | Service | Occurrences | File |
|---|---|---|---|
| @maple/mcp/errors/McpQueryError (6 issues) | maple-chat | 1.3k | apps/electric-sync/src/shapes/registry.ts |
| @maple/mcp/errors/McpQueryError (4 issues) | maple-ai | 349 | apps/electric-sync/src/shapes/registry.ts |
After this merges, Maple checks whether they stop.
Production traffic of the changed files (last 7 days)
| File | Calls/day | Busiest operations |
|---|---|---|
packages/backend/src/services/alerts/delivery/runTransport.ts |
2.8k | POST 1.8k/day, 2.2% errPOST 1.1k/day, 0.1% err |
packages/backend/src/services/alerts/NotificationDispatcher.ts |
61 | NotificationDispatcher.dispatchOne 61/day, 0.0% err |
apps/web/src/page/integrations/command.ts |
17 | LoadIntegrationsHazelStatus 17/day, 0.0% err |
What was checked
- No reference to
HazelOAuthService,HAZEL_OAUTH_*,hazel-oauth,HazelIconor the removed hazel endpoints survives at the head SHA (grep) - No redirect loop:
chat-hazelis not inDATA_INTEGRATION_IDS(route/redirect.ts:39), pinned byroute/route.test.ts:71 providers.ts:182falls back for an unknown destination type, so a row the map no longer covers cannot render blank
9447a9b · Reply "won't fix" to dismiss a finding, or mention @maple-review-bot to ask about one.
Loading