[PR #9208] fix(ci): surface new packages in release notes #25404

Open
opened 2026-04-15 22:52:18 -05:00 by GiteaMirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/9208
Author: @gustavovalverde
Created: 4/15/2026
Status: 🔄 Open

Base: nextHead: fix/release-notes-new-packages


📝 Commits (1)

  • ce42489 fix(ci): surface new packages in release notes

📊 Changes

3 files changed (+71 additions, -16 deletions)

View changed files

📝 .github/prompts/release-notes-rewrite.md (+2 -2)
📝 .github/scripts/lib/pr-analyzer.ts (+4 -0)
📝 .github/scripts/release-notes.ts (+65 -14)

📄 Description

Summary

Fix the release-note pipeline so new packages like @better-auth/cimd get their own package section instead of being folded into another package.

What changed

  • add cimd package/domain mappings to the release-note analyzer
  • duplicate multi-package changeset entries across each affected package section instead of collapsing them to one package
  • mark packages that are new since the previous tag with
  • fall back to README links when a newly added package does not have a generated CHANGELOG.md yet
  • update the AI rewrite prompt so it preserves the new-package heading markers and generic reference links

Root cause

The @better-auth/cimd PR carried a multi-package changeset, but the analyzer did not recognize cimd as its own package. That caused the release notes to group the PR under @better-auth/oauth-provider. For brand-new packages, the formatter also assumed a CHANGELOG.md already existed, which is not true for @better-auth/cimd in v1.7.0-beta.1.

Impact

Future release notes will surface newly added packages as first-class sections, with a visible marker and a valid reference link, instead of burying them under adjacent packages.

Validation

  • node .github/scripts/release-notes.ts --version 1.7.0-beta.1 --branch HEAD --dry-run
  • pre-commit hooks on commit: spell, biome

Summary by cubic

Fixes the release-notes pipeline so new packages get their own section with clear markers and valid links. Prevents mis-grouping like @better-auth/cimd being folded under another package.

  • Bug Fixes
    • Added cimd scope/path mappings and resolved to @better-auth/cimd.
    • Duplicated multi-package changesets into each affected package section.
    • Marked packages added since the previous tag with in headings.
    • Used README links when no CHANGELOG.md exists; preferred CHANGELOG when available.
    • Updated the rewrite prompt to preserve new-package markers and reference links.

Written for commit ce42489f35. Summary will update on new commits.


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/better-auth/better-auth/pull/9208 **Author:** [@gustavovalverde](https://github.com/gustavovalverde) **Created:** 4/15/2026 **Status:** 🔄 Open **Base:** `next` ← **Head:** `fix/release-notes-new-packages` --- ### 📝 Commits (1) - [`ce42489`](https://github.com/better-auth/better-auth/commit/ce42489f35027a7a8997efa76411b9c20cfc7feb) fix(ci): surface new packages in release notes ### 📊 Changes **3 files changed** (+71 additions, -16 deletions) <details> <summary>View changed files</summary> 📝 `.github/prompts/release-notes-rewrite.md` (+2 -2) 📝 `.github/scripts/lib/pr-analyzer.ts` (+4 -0) 📝 `.github/scripts/release-notes.ts` (+65 -14) </details> ### 📄 Description ## Summary Fix the release-note pipeline so new packages like `@better-auth/cimd` get their own package section instead of being folded into another package. ## What changed - add `cimd` package/domain mappings to the release-note analyzer - duplicate multi-package changeset entries across each affected package section instead of collapsing them to one package - mark packages that are new since the previous tag with `✨` - fall back to `README` links when a newly added package does not have a generated `CHANGELOG.md` yet - update the AI rewrite prompt so it preserves the new-package heading markers and generic reference links ## Root cause The `@better-auth/cimd` PR carried a multi-package changeset, but the analyzer did not recognize `cimd` as its own package. That caused the release notes to group the PR under `@better-auth/oauth-provider`. For brand-new packages, the formatter also assumed a `CHANGELOG.md` already existed, which is not true for `@better-auth/cimd` in `v1.7.0-beta.1`. ## Impact Future release notes will surface newly added packages as first-class sections, with a visible marker and a valid reference link, instead of burying them under adjacent packages. ## Validation - `node .github/scripts/release-notes.ts --version 1.7.0-beta.1 --branch HEAD --dry-run` - pre-commit hooks on commit: `spell`, `biome` <!-- This is an auto-generated description by cubic. --> --- ## Summary by cubic Fixes the release-notes pipeline so new packages get their own section with clear markers and valid links. Prevents mis-grouping like `@better-auth/cimd` being folded under another package. - **Bug Fixes** - Added `cimd` scope/path mappings and resolved to `@better-auth/cimd`. - Duplicated multi-package changesets into each affected package section. - Marked packages added since the previous tag with ✨ in headings. - Used `README` links when no `CHANGELOG.md` exists; preferred `CHANGELOG` when available. - Updated the rewrite prompt to preserve new-package markers and reference links. <sup>Written for commit ce42489f35027a7a8997efa76411b9c20cfc7feb. Summary will update on new commits.</sup> <!-- End of auto-generated description by cubic. --> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-15 22:52:18 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#25404