[sentry-junior]

Category summaries in the 3.0.0 release preview were vague ("Release communication…", "Internal maintenance…"), and the breaking-change summary didn't say why the change was breaking. The model only had PR titles to work with, and the prompt pushed category summaries toward abstract themes.

• Each changelog entry now goes to the model with a condensed copy of its PR description: HTML comments and code blocks are removed, whitespace is collapsed, and it's capped at 600 characters. The description is context only and never shows up in the rendered changelog. Entries that come from a Changelog Entry section or #body-in-changelog don't get one, since their curated text is already the entry.
• The prompt now asks scope and category summaries to name the specific features, targets and options that changed, bans vague umbrella phrases, and asks breaking-change summaries to say what users must change when the data says so. It also tells the model not to guess when the data doesn't say. The top-level release overview instructions are unchanged because that output was already good.
• serializeChangelog now passes each group's source PRs alongside its rendered items. The important-title and description lookups both come from that one list, so there's no more index-offset merging.

I left reasoning level / model settings alone. Whether those need tuning is easier to judge once a real release has run with the richer input.

Closes #917

via adm.

--

View Junior Session [Sentry]

[github-actions]

PR Preview Action v1.8.1
Preview removed because the pull request was closed.
2026-10-22 10:22 UTC

[MathurAditya724]

Reviewed all five changed files and the surrounding generation, hierarchy, provider and rendering paths at fc2585d. The Markdown-parser update fixes the fence/comment cases from the earlier revision. The 150 affected tests, TypeScript check and focused ESLint check pass locally; current CI, including live summarizer replay and five-platform artifact verification, also passes. One actionable issue remains in shortcode normalization, noted inline.

[MathurAditya724]

Reviewed the final head and verified the fix for the reported shortcode issue: inline-code configuration values are retained, with regression coverage. No remaining blocking findings. All 28 applicable CI checks pass, including live summarizer replay and five-platform artifact verification; the 150 focused tests, typecheck, lint and build also pass locally.