[sentry-junior]

Adds a changelog entry for Sentry CLI 0.46.0, the first release from getsentry/toolkit. 0.47.0 was split out into #231, so each minor release gets its own entry.

The entry covers new features: batch issue view/issue explain, event attachments and sentry wasm-split. It also lists fixes for older traces, project pagination, sourcemap injection, old Node.js versions and deleted working directories, plus the move to Toolkit and installer changes.

The 0.46.0 release notes only describe the repository move, but that release also ships the 60 getsentry/cli commits after 0.45.0, so the entry includes those as well. Each item was checked against the code at cli@0.46.0; the Toolkit PRs that only shipped in 0.47.0 (#1366, #1369, #1372, #1392, #1365, #1370, #1403) moved to #231.

Changes in the split: slug and file renamed to sentry-cli-0-46-0 (never published, so no existing entry is affected), and article links now use github.com instead of linear.review.

Attribution note: getsentry/cli#1642 and #1643 were opened by a bot. They're credited to the human commit authors that GitHub lists for them.

Validation: pnpm changelog:validate passes. The body compiles with compileMDX and the app's mdxOptions and renders to static HTML. Not checked: rendering in the Vercel preview.

The proposed publication date is 2026-10-20. The entry goes live only when this PR is merged.

product=cli
source_repo=getsentry/toolkit
releases=cli@0.46.0
cli@0.46.0 sha=41e649e9 published=2026-10-01T17:20:54Z
imported_history=getsentry/cli 0.45.0...c1337081

via bete.

--

View Junior Session [Sentry]

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
sentry-changelog	Ready	Preview	Oct 19, 2026 6:52pm UTC

[cursor]

This change publishes one new changelog article after merge. The plan checks new article page loads, list page failures, article compile errors, and the public JSON API. An issue escalates when list or article page failures rise or compile errors appear.

Rollout complete

Services: sentry-changelog.

Plan

What changed

Requests to /changelog/sentry-cli-0-46-0/ return the new CLI 0.46.0 article. The article also appears on the list, the RSS feed, and GET /api/changelogs.

sentry-changelog must deploy to production. Production pages read the database, not the Markdown file. The article is live after the Sync Changelog job writes slug sentry-cli-0-46-0 and revalidates the cache. The dated 2026-10-20 field does not hide the row. The entry can appear as soon as that sync finishes.

Risk

Bad MDX on this slug shows "This entry could not be displayed" on the article. A thrown getChangelogs query can fail the list, RSS, and related entries for every reader. A thrown getChangelog query can fail sibling article pages. GET /api/changelogs can return 500 to broadcast consumers. A failed sync rolls back the whole upsert run. Existing articles stay. The new article stays unpublished.

Intended effect

The change worked when production GET traces for /changelog/sentry-cli-0-46-0/ rise above zero and succeed. Absent looks like those traces stay at zero after traffic hits the URL, or the traces fail, or changelogDetailMdx errors include slug sentry-cli-0-46-0. If no client requests the new URL, leave this axis unknown.

Signal	Baseline	Window	Rule	Source
Successful GET traces whose URL contains /changelog/sentry-cli-0-46-0/	0 requests	2026-10-12T19:15Z to 2026-10-19T19:15Z	Rise above 0. Failure rate must stay 0.	Sentry org sentry project changelog: environment:production *sentry-cli-0-46-0*
changelogDetailMdx errors for slug sentry-cli-0-46-0	0 events	2026-10-12T19:15Z to 2026-10-19T19:15Z	Hold at 0. Any event means the article body failed to compile.	Sentry org sentry project changelog: environment:production changelog_stage:changelogDetailMdx

Regression watch

This diff can break the shared list and article paths that compile MDX and query Changelog rows. Watch those paths, not generic host health. POST /changelog/[slug] already fails in a small band from CHANGELOG-8T database errors. Do not treat that existing band as this change.

Signal	Baseline	Window	Rule	Source
GET /changelog failure rate	0%	2026-10-17T19:15Z to 2026-10-19T19:15Z	Hold at 0%. A rise is a list outage. RSS uses the same getChangelogs query.	Sentry org sentry project changelog: environment:production is_transaction:true transaction:"GET /changelog"
GET /changelog p95 duration	1000-1020ms in the last 48h. 7d p95 was 2410ms and may be seasonal.	2026-10-17T19:15Z to 2026-10-19T19:15Z	Hold the 48h band. Escalate if p95 rises above 2410ms.	Same query as the list failure rate
GET /changelog volume	0.97-1.00 TPM	2026-10-18T19:15Z to 2026-10-19T19:15Z and 2026-10-17T19:15Z to 2026-10-19T19:15Z	Hold the band. A crash of this volume with a failure-rate rise means readers cannot open the list.	Same query as the list failure rate
GET /changelog/[slug] failure rate	0%	2026-10-12T19:15Z to 2026-10-19T19:15Z	Hold at 0%. A rise is a sibling article outage.	Sentry org sentry project changelog: environment:production is_transaction:true transaction:"GET /changelog/[slug]"
GET /changelog/[slug] p95 duration	880-900ms	2026-10-18T19:15Z to 2026-10-19T19:15Z, 2026-10-17T19:15Z to 2026-10-19T19:15Z, and 2026-10-12T19:15Z to 2026-10-19T19:15Z	Hold the band.	Same query as the slug failure rate
changelogDetailMdx and getChangelogSummaries compile errors	0 events	2026-10-12T19:15Z to 2026-10-19T19:15Z	Hold at 0. These tags fire when article or list MDX compile fails.	Sentry org sentry project changelog: environment:production changelog_stage:changelogDetailMdx and changelog_stage:getChangelogSummaries
GET /api/changelogs failure rate	0%	2026-10-17T19:15Z to 2026-10-19T19:15Z	Hold at 0%. A rise means broadcast consumers cannot read published entries.	Sentry org sentry project changelog: environment:production is_transaction:true transaction:"GET /api/changelogs"
GET /api/changelogs p95 duration	800-805ms	2026-10-18T19:15Z to 2026-10-19T19:15Z and 2026-10-17T19:15Z to 2026-10-19T19:15Z	Hold the band.	Same query as the API failure rate

getChangelog already records about 6 production errors per 24h. Pair a rise in that tag with the slug failure rate. Do not page on the tag alone.

Not observable

The Sync Changelog GitHub Action result is not in Sentry. If no client requests /changelog/sentry-cli-0-46-0/, publication cannot be confirmed from traces. Wording accuracy of the CLI notes has no telemetry. Rendering of the Sentry What's New panel is not in this project.

[cursor]

Verified in production

• The new CLI article loaded successfully, and list, article, and API paths did not fail.