Improve AI-generated changelog category summaries #917

The AI-generated per-category changelog summaries can be vague or opaque, even when the top-level release overview is useful. In the craft@3.0.0 release, the breaking-changes summary said workspace publishing was added without explaining why it is breaking, while other summaries used phrases like “Release communication” and “Internal maintenance.”

• Make category summaries concrete and informative, and ensure breaking-change summaries explain what makes the change breaking.
• The current feature uses PR titles only. As proposals to investigate, the discussion suggested including PR bodies and/or improving the prompt or reasoning level.
• Keep the scope focused on category/accordion summaries; the top-level overview was considered acceptable.

Example: getsentry/publish#9964; AI summary implementation: getsentry/craft#913.

via adm.

--

View Junior Session [Sentry]