Mohamed BoudraandGitHub
90d386b88e
* Restore changelog entries for betas
Beta users check release notes, so each beta now updates an in-place
CHANGELOG.md entry that promotion overwrites with the final stable entry
— no -beta.N heading is left behind. The release machinery already
parses beta headings and syncs them; this restores the policy in the
docs and the release-beta skill, reversing the docs side of 28415b354.
* Spell out in-place beta overwrite in the promotion checklist
The stable checklist said only "update CHANGELOG.md", so a promotion
followed by the letter could stack a fresh entry on top of the
-beta.N block — the stale heading the policy forbids. Make the
promotion path overwrite-in-place explicit, matching the beta checklist.
798 B
798 B
name, description, user-invocable
| name | description | user-invocable |
|---|---|---|
| release-beta | Cut a beta release of Paseo. Use when the user says "release beta", "cut a beta", "ship a beta", "beta release", or "/release-beta". Betas are release candidates on the beta channel — they carry an in-place changelog entry, don't move the website download target, and publish npm only on the beta dist-tag. | true |
Release beta
Read docs/release.md in the Paseo repo and follow the Beta flow section end-to-end. Run the Beta release completion checklist at the bottom of that doc.
Key rules the doc enforces — each beta updates an in-place CHANGELOG.md entry (## X.Y.Z-beta.N) that gets overwritten at promotion (never leave a stale -beta.N heading behind), and betas publish npm only with the explicit beta dist-tag.