Skip to content

Commit 674e3ca

Browse files
t3dotggclaude
andcommitted
test(web): pin the npm wait floor for update everything
Co-Authored-By: Claude Opus 5.5 <[email protected]>
1 parent e6ca170 commit 674e3ca

3 files changed

Lines changed: 19 additions & 15 deletions

File tree

‎apps/web/src/components/sidebar/updateEverything.logic.test.ts‎

Lines changed: 9 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -88,15 +88,17 @@ describe("collectServerUpdateTargets", () => {
8888

8989
it("waits for npm only for hosts that install from it or when the release may lack archives", () => {
9090
const hosts = [
91-
machine("archive-service", "0.1.4", "boot-service"),
92-
machine("npm-service", "0.0.40", "boot-service"),
93-
machine("legacy-respawn", "0.1.4", "respawn"),
94-
machine("desktop", "0.1.4", "desktop-managed"),
91+
machine("archive-service", "0.0.41-nightly.20260914.1700", "boot-service"),
92+
machine("npm-service", "0.0.41-nightly.20260914.1687", "boot-service"),
93+
machine("legacy-respawn", "0.1.4-nightly.20261027.3796", "respawn"),
94+
machine("desktop", "0.1.4-nightly.20261027.3796", "desktop-managed"),
9595
];
9696
const waits = (releaseArchivesPublished: boolean) =>
97-
collectServerUpdateTargets(hosts, "0.1.5", releaseArchivesPublished).waitForNpm.map(
98-
(target) => target.serverLabel,
99-
);
97+
collectServerUpdateTargets(
98+
hosts,
99+
"0.1.5-nightly.20261029.3873",
100+
releaseArchivesPublished,
101+
).waitForNpm.map((target) => target.serverLabel);
100102

101103
expect(waits(true)).toEqual(["npm-service", "legacy-respawn"]);
102104
expect(waits(false)).toEqual(["archive-service", "npm-service", "legacy-respawn"]);

‎docs/operations/release.md‎

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -432,9 +432,10 @@ release archives, and then its npm launcher, available before users can receive
432432
The workflow enforces this ordering:
433433

434434
1. `release` publishes the GitHub Release with the CLI archives and `SHA256SUMS`. Every channel
435-
uploads to a draft and publishes only after all assets are attached, so a version in the
436-
desktop update feed always has its archives. **Update everything** relies on this to update
437-
background-service hosts before npm has the version.
435+
uploads to a draft and publishes only after all assets are attached, so a new version in the
436+
desktop update feed already has its archives. **Update everything** relies on this to update
437+
background-service hosts before npm has the version. Rerunning `release` after publication
438+
replaces assets in a public release, so service updates can fail until the upload finishes.
438439
2. `publish_cli` publishes the `t3@<version>` launcher, which downloads from that release, on every
439440
channel.
440441
3. `deploy_web` depends on both before moving the hosted channel to the new client.

‎docs/user/updating.md‎

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -22,11 +22,12 @@ restart from the update button when you are ready. A server still restarting
2222
finishes on its own, and the button keeps showing it after the desktop app
2323
restarts.
2424

25-
Remote desktop apps never wait for npm. Background services do not wait either
26-
when the version comes from the desktop app's update. Other server updates
27-
appear only after that version is published to npm. The confirmation lists each machine it skips
28-
and why, such as a machine that is offline or needs a manual update. Use
29-
**Settings → Environments** for those.
25+
Remote desktop apps never wait for npm. When the desktop app offers the update,
26+
background services update right away too. Other servers, including background
27+
services from before September 2026, update only after that version is
28+
published to npm. The confirmation lists each machine it skips and why, such as
29+
a machine that is offline or needs a manual update. Use **Settings →
30+
Environments** for those.
3031

3132
If a desktop app restarts on its old version, T3 Code tells you the update did
3233
not apply. It does not install that version again on its own, even when another

0 commit comments

Comments
 (0)