Unified · Split
| @@ -67,6 +67,13 @@ Lead with **user-visible stories**, not commit subjects. Group related commits i · 66 unmodified lines | |||
| 67 | - The `.changeset/*.md` body shows up in the Version Packages PR description. Use the same content (or a condensed version) as the release-notes file. | 67 | - The `.changeset/*.md` body shows up in the Version Packages PR description. Use the same content (or a condensed version) as the release-notes file. |
| 68 | - Frontmatter is `"executor": patch` (or `minor`/`major` if owner says so). | 68 | - Frontmatter is `"executor": patch` (or `minor`/`major` if owner says so). |
| 69 | 69 | ||
| 70 | ### Post-release archival (manual) | ||
| 71 | After a release publishes, rename `apps/cli/release-notes/next.md` → `apps/cli/release-notes/v<version>.md` and commit on `main` (or in a small follow-up PR). This: | ||
| 72 | - Preserves the historical notes file-by-version (matches `release.ts`'s preferred lookup path). | ||
| 73 | - Resets `next.md` absence so the next cycle starts from a blank file — no chance of last release's content leaking into the next one. | ||
| 74 | |||
| 75 | `release.ts` falls back to `next.md` if `v<version>.md` is missing, so skipping the rename won't break a publish; it just leaves stale content in `next.md` for the next release. | ||
| 76 | |||
| 70 | ## Beta release flow | 77 | ## Beta release flow |
| 71 | 78 | ||
| 72 | ``` | 79 | ``` |