
Release Beta
- 418 installs
- 12.1k repo stars
- Updated August 4, 2026
- getpaseo/paseo
Run a disciplined beta release with Paseo checklists, versioning, rollout gates, and feedback capture before general availability.
About
Guides releasing a beta through Paseo: defining rollout gates, versioning, stakeholder checklists, monitoring expectations, and feedback capture so SaaS or mobile products ship a controlled preview before general availability.
- Beta rollout checklist
- Version and channel gating
- Release note preparation
- Feedback loop setup
- Pre-GA ship discipline
Release Beta by the numbers
- 418 all-time installs (skills.sh)
- Ranked #57 of 248 Release Management skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/getpaseo/paseo --skill release-betaAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 418 |
|---|---|
| repo stars | ★ 12.1k |
| Last updated | August 4, 2026 |
| Repository | getpaseo/paseo ↗ |
What it does
Run a disciplined beta release with Paseo checklists, versioning, rollout gates, and feedback capture before general availability.
Files
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.