You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Migrate alert commands off legacy APIs by Aug 17 #1274
Finish moving sentry alert off legacy alerts APIs before they are retired on 2026-08-17.
Production traffic from CLI 0.38.0 (User-Agent: sentry-cli/0.38.0 … node/…) is already hitting those endpoints via first-class sentry alert commands in src/lib/api/alerts.ts, not only via sentry api.
The API migration this issue asks for is already fully landed on main — no code change left to make here.
Audited packages/cli/src/lib/api/alerts.ts (repo is now a pnpm monorepo): every read and write for both issue alerts and metric alerts targets the new endpoints. Zero live call sites remain on the retiring /projects/{org}/{project}/rules/ or /organizations/{org}/alert-rules/ paths — those strings now only appear in migration-history comments.
Operation
Endpoint now
issue alert list/get/create/edit/delete
/organizations/{org}/workflows/
metric alert list/get/edit/delete
/organizations/{org}/detectors/
metric alert create
/projects/{org}/{project}/detectors/
Landed via #1275 (metric reads) and #1338 (metric mutations); issue-alert mutations were already on /workflows/. The only remaining /alerts/rules/ references are in sentry-urls.ts, which builds Sentry web UI links, not API requests — those are correct and unaffected.
Verified locally: the alert unit suite (test/lib/api/alerts.test.ts + test/commands/alert) is 171/171 green on current main.
Remaining scope — not a code change:#1338 merged on 2026-08-02, after the 0.40.0 release (2026-07-31), so the metric-mutation migration isn't in a published version yet. A CLI release cut from current main needs to ship before the 2026-08-17 cutoff so users can upgrade. That's a maintainer/craft release action, so I'm leaving it to you rather than opening an empty PR.
If there's a specific gap you're still seeing on legacy endpoints (e.g. something from #1142), point me at it and I'll take it.
Activity
fix(alerts): read metric alert rules from org-scoped /detectors/ (#1275)
fix(alerts): migrate metric alert mutations to detectors API (#1338)
BYK commentedon Aug 2, 2026
Jared, is this fully done now so we can close the issue?
jared-outpost commentedon Aug 3, 2026
The API migration this issue asks for is already fully landed on
main— no code change left to make here.Audited
packages/cli/src/lib/api/alerts.ts(repo is now a pnpm monorepo): every read and write for both issue alerts and metric alerts targets the new endpoints. Zero live call sites remain on the retiring/projects/{org}/{project}/rules/or/organizations/{org}/alert-rules/paths — those strings now only appear in migration-history comments./organizations/{org}/workflows//organizations/{org}/detectors//projects/{org}/{project}/detectors/Landed via #1275 (metric reads) and #1338 (metric mutations); issue-alert mutations were already on
/workflows/. The only remaining/alerts/rules/references are insentry-urls.ts, which builds Sentry web UI links, not API requests — those are correct and unaffected.Verified locally: the alert unit suite (
test/lib/api/alerts.test.ts+test/commands/alert) is 171/171 green on currentmain.Remaining scope — not a code change: #1338 merged on 2026-08-02, after the
0.40.0release (2026-07-31), so the metric-mutation migration isn't in a published version yet. A CLI release cut from currentmainneeds to ship before the 2026-08-17 cutoff so users can upgrade. That's a maintainer/craft release action, so I'm leaving it to you rather than opening an empty PR.If there's a specific gap you're still seeing on legacy endpoints (e.g. something from #1142), point me at it and I'll take it.