Repository navigation
Keep only stable and beta Release Channels #990
Description
Parent
Spec: 1.0 tree cleanup and release contracts
What to build
Make installers, daemon upgrade resolution, release scripts, and CI agree on stable and beta, using the tag semantics settled by the map's release decision.
Acceptance criteria
-
latestandnightlyare not accepted as Release Channels or emitted by release tooling. - Installer/channel tests prove stable resolves the highest stable release and never a prerelease; beta resolves its intended prerelease.
Activity
nick-potts commentedon Sep 24, 2026
Scope added by Version number and tag semantics for the first stable release, points 6–9:
promote-release.shonly advances a pointer to a higher semver tag; a stable Publish also advancesbetawhen it's higher; upgrading through a channel never downgrades (only an exact version can); the resolver rejects a pre-release read fromstable.nick-potts commentedon Sep 24, 2026
Scope addition from How the stable pointer survives a breaking release: daemons resolve per-line pointers
ployz.sh/v<major>/<channel>. Only the liveinstall.shreads the unscopedployz.sh/<channel>. Release tooling publishes both. The tests should cover the line-scoped URL.