You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 4219491
Browse filesBrowse the repository at this point in the historyBrowse files
fix(release): the feed job tells a GitHub outage from a stale pointer
Council round 2:
- A response body that fails to arrive no longer marks the pointer stale,
and no longer blocks the pointer repair when it is the feed's body.
- The job reports an unreadable feed and a hidden nightly as different
failures, and publishes the update-feed release if someone drafted it.
- Docs: the rollback steps cover a paused schedule and npm's nightly
dist-tag, and the release order no longer says previews publish to npm.
Co-Authored-By: Claude Fable 5.2 <[email protected]>
echo "::error::releases.atom could not be read, or its first nightly is not $RELEASE_TAG. Nightly installs older than 0.1.10-nightly.20261112.4603 cannot reach it. A preview from a branch not rebased onto main is the usual cause. See docs/operations/release.md#update-feed."
1102
+
if [[ "$FEED" == "unreadable" ]]; then
1103
+
echo "::error::releases.atom could not be read, so this run could not check it. No tag cleanup is needed unless a later run reports a hidden nightly."
1104
+
else
1105
+
echo "::error::The first nightly in releases.atom is not $RELEASE_TAG. Nightly installs older than 0.1.10-nightly.20261112.4603 cannot reach it. A preview from a branch not rebased onto main is the usual cause. See docs/operations/release.md#update-feed."
1106
+
fi
1100
1107
exit 1
1101
1108
1102
1109
# The `t3` npm package is a launcher that downloads this version's CLI
Copy file name to clipboardExpand all lines: docs/operations/release.md
+9-7Lines changed: 9 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ the version.
19
19
- push tag matching `v*.*.*` for a stable release of an explicit commit
20
20
- scheduled nightly check every 30 minutes
21
21
- 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. It publishes nothing to npm. 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, 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 a new preview is downloading the draft by hand as a maintainer: a draft's files are not public, so `T3CODE_CHANNEL=preview` and `t3 update --channel preview` see only previews published before this rule, and `npx t3@preview` no longer works. Rebase a branch onto `main` before dispatching a preview from it. The run uses the branch's own `release.yml`, and an older copy publishes the preview with a tag. 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. It publishes nothing to npm. 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, 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 ways onto a new preview are by hand: the draft release, which maintainers can open, and the run's Actions artifacts. A draft's files are not public, so `T3CODE_CHANNEL=preview` and `t3 update --channel preview` see only previews published before this rule, and `npx t3@preview` fails while npm's `preview` dist-tag names a draft. Rebase a branch onto `main` before dispatching a preview from it. The run uses the branch's own `release.yml`, and an older copy publishes the preview with a tag. 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.
23
23
- A manual stable release builds the commit of the latest published nightly, not `main` HEAD.
24
24
Nightly is the release candidate: verify the nightly, then promote it. Merges to `main` keep
25
25
landing while you verify and never leak into the stable build.
@@ -436,13 +436,13 @@ release archives, and then its npm launcher, available before users can receive
436
436
437
437
The workflow enforces this ordering:
438
438
439
-
1.`release` publishes the GitHub Release with the CLI archives and `SHA256SUMS`. Every channel
440
-
uploads to a draft and publishes only after all assets are attached, so a new version in the
439
+
1.`release` publishes the GitHub Release with the CLI archives and `SHA256SUMS`. Stable and
440
+
nightly upload to a draft and publish only after all assets are attached, so a new version in the
441
441
desktop update feed already has its archives. **Update everything** relies on this to update
442
442
background-service hosts before npm has the version. Rerunning `release` after publication
443
443
replaces assets in a public release, so service updates can fail until the upload finishes.
444
-
2.`publish_cli` publishes the `t3@<version>` launcher, which downloads from that release, on every
445
-
channel.
444
+
2.`publish_cli` publishes the `t3@<version>` launcher, which downloads from that release, on
445
+
stable and nightly. A preview stays a draft and publishes no launcher.
446
446
3.`deploy_web` depends on both before moving the hosted channel to the new client.
447
447
`build_web` builds that client earlier with `vercel deploy --prod --skip-domain`, which
448
448
leaves the custom domains alone but moves the project's own `*.vercel.app` production
@@ -494,8 +494,10 @@ anything users should not be offered stays a draft or uses one rolling tag, like
494
494
495
495
To pull a bad nightly, delete its release and tag, then run
496
496
`gh release delete-asset update-feed nightly.json`. Installs fall back to the feed until the next
497
-
tick rewrites the pointer. Without that command, installs that know the pointer report an update
498
-
error until that tick.
497
+
unpaused tick or manual nightly rewrites the pointer. Without that command, installs that know the
498
+
pointer report an update error until then. If npm's `nightly` dist-tag still names the pulled
499
+
build, also move it to the last good one with `npm dist-tag add t3@<version> nightly`. The channel
500
+
switch in Settings reads that tag and refuses an older desktop build.
0 commit comments