Skip to content

Commit c8d5767

Browse files
t3dotggclaude
andcommitted
docs(release): the update feed lists git tags, so a preview must never get one
Co-Authored-By: Claude Fable 5.2 <[email protected]>
1 parent 5aa4156 commit c8d5767

2 files changed

Lines changed: 3 additions & 3 deletions

File tree

‎.github/workflows/release.yml‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1036,8 +1036,8 @@ jobs:
10361036
# The action keeps a stable release a draft until its assets finish uploading, but publishes a
10371037
# prerelease first. Desktop clients update connected servers from the CLI archives as soon as
10381038
# they see the release, so a prerelease also goes public only once every asset is attached.
1039-
# Previews stay drafts: GitHub orders same-day releases by semver, so public `preview` tags
1040-
# outrank `nightly` ones and push nightlies out of the 10-entry releases.atom older updaters read.
1039+
# Previews stay drafts, because a draft has no git tag. releases.atom lists the 10 newest tags,
1040+
# same-day `preview` tags sort above `nightly` ones, and older updaters find nightlies only there.
10411041
- name: Publish prerelease
10421042
if: needs.preflight.outputs.is_prerelease == 'true' && needs.preflight.outputs.release_channel != 'preview'
10431043
env:

‎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 GitHub orders same-day releases by semver, so a public `preview` tag outranks `nightly` and a few previews push every nightly out of the 10-entry `releases.atom` that older nightly updaters read. 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. `releases.atom` lists the 10 newest tags in the repository, same-day `preview` tags sort above `nightly` ones, and nightly updaters older than 0.1.10-nightly.20261112.4603 find updates only in that feed, so ten published previews hide every nightly from them. Do not publish a preview draft by hand; converting it back to a draft afterwards leaves the tag in the feed until the tag is deleted. 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.
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)