Update the release notes file at `apps/docs/content/releases/next.mdx` based on PRs merged to main since the previous release, or archive `next.mdx` to a versioned file when a new version is published.
This skill handles the operational tasks of maintaining release notes: adding new PR entries to next.mdx and archiving releases when a new version is published.
Run the status script to determine versions and diff branch:
.claude/skills/update-release-notes/scripts/get-changelog-status.sh
This returns:
diff_branch (e.g., v4.3.x) - the branch to diff againstlatest_release - the most recent published releaseIf a new release was published since last_version in next.mdx:
next.mdx content to vX.Y.0.mdx (e.g., v4.3.0.mdx)title to the versionnext.mdx:
last_version field to the new releaseGet PR numbers merged since the release branch:
.claude/skills/update-release-notes/scripts/get-new-prs.sh <diff_branch>
Batch fetch all PR information:
.claude/skills/update-release-notes/scripts/fetch-pr-batch.sh <pr1> <pr2> ...
For each PR not already in next.mdx:
Check that:
last_version fieldThe next.mdx frontmatter includes a last_version field that tracks the most recent published release. This determines which PRs are "new" and need to be added.
../shared/release-notes-guide.md for guidance on what a release notes article should contain and how to format it.scripts/ for automation helpers