How these release notes are assembled

Where the notes come from

Every entry in the archive corresponds to a real GitHub release object published on the public hashgraph-online/hol-guard repository. A git tag by itself is not a release: pages exist only for releases that GitHub actually published, and draft releases are never shown. The original release and its tag are linked from each page so you can always compare our notes with the source.

How they are aggregated

The upstream release notes are edited into a short factual summary and grouped changes, published on this site the moment a release is verified. The original source prose is preserved separately from our edited summaries, and each change links back to the public pull request or commit that proves it. Contributor credits are derived only from verifiable public evidence — pull-request authorship, verified commit authorship, or verified co-author lines — never from thanks text, display names, or release metadata. How contributor credit works explains that system in detail.

When a release cannot be compared with an earlier published release on the same channel — for example, when the predecessor is a tag without a release object — the page says “Comparison unavailable” instead of linking something unverifiable.

What they cover

The stable archive covers published stable releases; the preview archive covers published early-access releases. One version per page: patch releases are never merged into each other, so the page for a version always describes exactly that version. When part of a release cannot yet be verified — for example, contributor attribution that is still being checked — the page says so explicitly rather than presenting an incomplete picture as complete.

How fresh they are

Pages are served from a verified snapshot of the release history, refreshed from the public repository on a regular schedule rather than fetched live on every visit. Each release page is dated by the release’s own original publication date, which never changes after publication; editorial corrections carry their own update trail. If the snapshot cannot be reached, the archive says so instead of showing stale or unverified data. The newest entries are also available as an RSS feed.

Corrections

Something wrong or missing in a release page? Corrections and credit removals are durable decisions: once made, they apply everywhere the notes appear. See corrections and removal for how to reach the maintainers.