Commit f0f282c
chore(main): release 0.1.0-preview.1 (#7)
* chore(main): release 0.1.0-preview.1
* chore(changelog): keep one 0.1.0-preview.1 heading
CHANGELOG.md carried two headings for the same version: a hand-written
"0.1.0-preview.1 (2026-09-04)" already on main, and the one release-please
generates for this release, "0.1.0-preview.1 (2026-09-08)". One version with
two headings and two dates splits the release notes, and whichever tool reads
the changelog for the published release notes would pick up only one of them.
Merged into the generated heading, which carries the real release date. The
four hand-written bullets describe what the package actually contains and the
generated entries do not restate them, so they are kept as the section's
summary above the conventional-commit Features and Bug Fixes lists. Nothing was
dropped from either section.
The stale entry was a placeholder rather than a record of a shipped release:
there is no v0.1.0-preview.1 tag, no GitHub release, the package has never been
pushed to NuGet, and main's .release-please-manifest.json is still {}. So the
right fix is to merge the headings, not to bump the version.
Addresses the CodeRabbit review comment on CHANGELOG.md:3.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016jgqTmscEnkgmAp1TkNFpG
---------
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>1 parent 17f74db commit f0f282c
2 files changed
Lines changed: 12 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1 | | - | |
| 1 | + | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1 | 1 | | |
2 | 2 | | |
3 | | - | |
| 3 | + | |
4 | 4 | | |
5 | 5 | | |
6 | 6 | | |
7 | 7 | | |
8 | 8 | | |
| 9 | + | |
| 10 | + | |
| 11 | + | |
| 12 | + | |
| 13 | + | |
| 14 | + | |
| 15 | + | |
| 16 | + | |
| 17 | + | |
| 18 | + | |
0 commit comments