You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
scripts/extract-changelog-section.ts uses first-indexOf heading match while ## [0.4.0], ## [0.3.0], ## [0.2.0] each appear twice — release notes are correct only by accident of ordering. Count matches and throw on >1, with a test over the real CHANGELOG.
No gate relates headings, git tags, and package.json version: tags stop at v0.10.0 (= last npm publish for liteship/create-liteship; @liteship/* scopes never published), 0.14-0.17 carry dates with no tag, 0.20-0.24 are all "(unreleased)", and 0.18/0.19 have no blocks despite README/ARCHITECTURE dating the Effect shed and rename to them.
Root cause of the version inflation: the api-surface gate correctly demands a bump per public-surface change, but no release was ever cut after 0.10.0 — 14 unreleased minors piled up. First publish of 0.24.0 closes the gap; the gate then keeps the ledger honest.
Three connected defects:
scripts/extract-changelog-section.tsuses first-indexOfheading match while## [0.4.0],## [0.3.0],## [0.2.0]each appear twice — release notes are correct only by accident of ordering. Count matches and throw on >1, with a test over the real CHANGELOG.liteship/create-liteship;@liteship/*scopes never published), 0.14-0.17 carry dates with no tag, 0.20-0.24 are all "(unreleased)", and 0.18/0.19 have no blocks despite README/ARCHITECTURE dating the Effect shed and rename to them.