Update release notes

next.mdx

Process

1. Check status

.claude/skills/update-release-notes/scripts/get-changelog-status.sh

• diff_branch

  (e.g.,

  v4.3.x

  ) - the branch to diff against

• latest_release

  - the most recent published release
• Whether archival is needed

2. Handle archival (if needed)

last_version

next.mdx

1. Copy

   next.mdx

   content to

   vX.Y.0.mdx

   (e.g.,

   v4.3.0.mdx

   )
2. Update the frontmatter in the new file:
   • Set

     title

     to the version
   • Update dates
   • Add the GitHub release link after frontmatter
3. Reset

   next.mdx

   :
   • Update

     last_version

     field to the new release
   • Clear the content sections
   • Keep the file structure for accumulating new changes

3. Find new PRs

.claude/skills/update-release-notes/scripts/get-new-prs.sh <diff_branch>

4. Fetch PR details

.claude/skills/update-release-notes/scripts/fetch-pr-batch.sh <pr1> <pr2> ...

5. Update next.mdx

next.mdx

1. Check PR labels and body against the style guide's categorization rules
2. Skip PRs that should be omitted (see style guide)
3. Add entries to the appropriate section
4. Promote significant changes to featured sections when warranted

6. Verify

• PR links are correct
• Community contributors are credited
• Sections are in the correct order
• Breaking changes are marked with 💥

The

last_version

field

next.mdx

last_version

References

• Style guide: See

  ../shared/release-notes-guide.md

  for guidance on what a release notes article should contain and how to format it.
• Scripts: See

  scripts/

  for automation helpers