Release Notes Summary

Headless integration that regenerates an AI-summarised rollup of the last 30 days of release notes.

What it does

Harness ships release notes per module, continuously. Keeping a single up-to-date view of what changed recently, across everything, by hand does not scale, so this integration does it automatically: it reads the last 30 days of release notes across modules, categorises them with AI, and regenerates the landing page this describes.

This is the one integration in this space with no card, button, or visible UI of its own on the reader-facing page. It is headless — it reacts to an event and rewrites page content, rather than rendering anything a reader clicks.

Why it is triggered manually right now

The integration normally reacts to space_gitsync_completed, regenerating automatically the moment new release-note content lands from Git Sync. That event handler is disabled for the time being, so regeneration in this space currently only runs from the Regenerate now button declared in the integration's space configuration — the same manual path the code already exposed for testing a space that is not wired to Git Sync at all. Nothing about the regeneration logic changed, only what triggers it; re-enabling automatic regeneration later is a one-line code change, not a rebuild.

Why this page is separate from the page it explains

This page is the overlay: the explanation of what the integration does and why. Release Notes Summaries, nested beneath it, with one page per module underneath (Platform, Continuous Integration, Code Repository, and so on), is the integration's actual output — regenerated automatically, not hand-written, and not something to describe from the outside without risking drift between the explanation and the real behaviour.

That rule extends to the info banner at the top of the generated page. It used to be pasted here, on the overlay, which meant two places could say different things about how to read the summaries. It is written by renderLandingMarkdown in the integration itself now, so the banner regenerates with the content it explains instead of drifting from it — read it on the live page, not here.

This is what it looks like in action

Release Notes Summaries is the live regenerated output, not a mock-up of it — open it and the six module subpages underneath (release-notes/platform, release-notes/continuous-integration, and so on) are real, published, visible pages, each carrying real release-note content that the summary page links out to through View full release notes. Unlike the package selector's child pages, these are not hidden from navigation; they are ordinary nav entries in their own right, because a reader is meant to be able to browse straight to a module's full history, not only reach it by way of the summary.