Skip to content

Commit bea81ed

Browse files
t3dotggclaude
andcommitted
docs(release): say how the preview install paths fail on a draft
Co-Authored-By: Claude Fable 5.2 <[email protected]>
1 parent 3c5a5a9 commit bea81ed

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

‎docs/operations/release.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ the version.
1919
- push tag matching `v*.*.*` for a stable release of an explicit commit
2020
- scheduled nightly check every 30 minutes
2121
- manual `workflow_dispatch` with `channel=nightly`
22-
- manual `workflow_dispatch` with `channel=preview`, the maintainers' test train. It exercises the whole release flow (build, sign, notarize, smoke, publish) for a commit that end users must never receive, which is how an unmerged branch or a risky change gets a real release run before it lands. It builds the triggering commit with nightly's versioning under the `preview` prerelease identifier (`0.0.41-preview.<date>.<run>`) and leaves its GitHub prerelease as a draft, plus the npm packages under the `preview` dist-tag. It stays a draft because a draft has no git tag, and published preview tags hide nightlies from the updater (see [Update feed](#update-feed)). Do not publish a preview draft by hand. Preview is not on the schedule, no default npm dist-tag points at it, its desktop builds carry no update feed, and no updater manifest (`latest*.yml`, `nightly*.yml`, blockmaps) is attached, so a stable or nightly install cannot be offered one. The only way onto it is downloading the draft by hand as a maintainer; `npx t3@preview`, `T3CODE_CHANNEL=preview`, and `t3 update --channel preview` cannot reach a draft's assets. Each of those paths prints a warning, and the CLI asks for confirmation when the running build is not itself a preview. The release itself is named as a maintainer test build and its body is a warning rather than generated notes: a changelog of unmerged branch history is not a changelog, and nightly and stable notes are unaffected because each series resolves its previous tag within its own channel. The hosted web app, AUR, and Discord announcements are skipped. Keep it; it costs nothing when idle.
22+
- manual `workflow_dispatch` with `channel=preview`, the maintainers' test train. It exercises the whole release flow (build, sign, notarize, smoke, publish) for a commit that end users must never receive, which is how an unmerged branch or a risky change gets a real release run before it lands. It builds the triggering commit with nightly's versioning under the `preview` prerelease identifier (`0.0.41-preview.<date>.<run>`) and leaves its GitHub prerelease as a draft, plus the npm packages under the `preview` dist-tag. It stays a draft because a draft has no git tag, and published preview tags hide nightlies from the updater (see [Update feed](#update-feed)). Do not publish a preview draft by hand. Preview is not on the schedule, no default npm dist-tag points at it, its desktop builds carry no update feed, and no updater manifest (`latest*.yml`, `nightly*.yml`, blockmaps) is attached, so a stable or nightly install cannot be offered one. The only way onto it is downloading the draft by hand as a maintainer. A draft's files are not public, so `npx t3@preview` fails when its launcher downloads the release, and `T3CODE_CHANNEL=preview` and `t3 update --channel preview` find no preview release. The release itself is named as a maintainer test build and its body is a warning rather than generated notes: a changelog of unmerged branch history is not a changelog, and nightly and stable notes are unaffected because each series resolves its previous tag within its own channel. The hosted web app, AUR, and Discord announcements are skipped. Keep it; it costs nothing when idle.
2323
- A manual stable release builds the commit of the latest published nightly, not `main` HEAD.
2424
Nightly is the release candidate: verify the nightly, then promote it. Merges to `main` keep
2525
landing while you verify and never leak into the stable build.

0 commit comments

Comments
 (0)