update-release-notes

To automate release notes from merged PRs, this skill updates the next.mdx file with newly merged PR entries by retrieving PR data through gh and git diffs, formatting the entries as markdown, and appending them to your documentation.

Release note archival works by renaming the existing next.mdx file to a versioned vX.Y.0.mdx file, updating the frontmatter to preserve history, and resetting next.mdx to start the next release cycle.

Yes, you need git, gh, and jq installed to automate changelog generation because the Bash scripts rely on gh to fetch PR details, git to determine version diffs, and jq to parse the retrieved PR data.

No, you cannot use this workflow outside an apps/docs/releases structure because the scripts are hardcoded to find and update the release notes file specifically at apps/docs/content/releases/next.mdx.

The best way to track merged PRs for changelog updates is running the status script to determine the diff against the latest release, which identifies newly merged entries to fetch and format into the next.mdx file.

Your next.mdx release notes file may not update if the status script fails to determine the diff against the latest version, or if gh lacks the required permissions to fetch the merged PR data needed for formatting.