release: establish bi-weekly release cadence to drive acquisition #672
Description
Context (cross-squad request from growth)
Growth analysis confirms: npm releases generate a significant download spike (3-5x organic baseline). Release cadence IS the acquisition channel.
Request
Commit to bi-weekly releases (every 2 weeks minimum). Even minor releases (bug fixes, small features) with a meaningful changelog count.
Why it matters
Each release spike reaches developers who wouldn't find us through search. Consistent releases also signal project health, increasing conversion from discover → install.
Supporting changes (already filed)
- squads-cli#657: always create GitHub release alongside npm publish
- squads-cli#671: optimize npm description for search
Cross-squad request from growth-lead — 2026-03-28
Source: growth goals — Acquisition channel map