Skip to content

docs: use aztec-node's release notes in docs releases from v6.1.0 - #25777

Merged
alejoamiras merged 4 commits into
nextfrom
worktree-docs-labs-release-notes
Nov 8, 2026
Merged

alejoamiras merged 4 commits into
nextfrom
worktree-docs-labs-release-notes

Conversation

@alejoamiras

Copy link
Copy Markdown
Contributor

From v6.1.0, aztec-node publishes its changes as GitHub release notes. A docs release now fetches the notes for every tag in its range and checks that each breaking change ends up in the migration notes or the operator changelog, or is dismissed with a reason.

  • A small script downloads the notes as they are and records each release's status and last edit, so the release commit says which version of the notes it used.
  • The release, network-release and changelog skills read those notes, map each entry to the right page, and report what was covered and how each change was verified.

docs/scripts/labs_release_notes.mts lists the published releases and the
release and rc tags in (<from>, <to>] that <to> contains, and writes each
note verbatim with its status and updated_at. It does not parse the notes,
and a GitHub error fails the run instead of reading as missing notes.
… v6.1.0

The release skills collect aztec-node's release notes for the tags a cut
or a pin move spans, route each entry with one table, and require a
coverage table: every breaking entry ends in the migration notes, the
operator changelog, or a written dismissal. The syntax sweep report gains
a verified-by column. The notes are treated as an untrusted index: the
code at the tag wins and no link is copied from them.
…le file

One PR can carry several migration entries and older entries cite no PR,
so the PR only finds candidates. Searching the whole file also covers
earlier rc headings and the operator pages, which have no TBD section.
…hange

One symbol can change twice, so a matching symbol only finds candidates;
an existing entry covers a release-note entry when it describes the same
old and new syntax, behaviour or value.
@alejoamiras
alejoamiras requested a review from a team as a code owner November 6, 2026 18:11
@alejoamiras
alejoamiras merged commit eef9c89 into next Nov 8, 2026
16 checks passed
@alejoamiras
alejoamiras deleted the worktree-docs-labs-release-notes branch November 8, 2026 12:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants