Publish the release from the script #12

Merged

uwayss merged 1 commit from fix/release-script into main

2026-08-28 10:57:40 +00:00

uwayss commented

2026-08-28 10:57:01 +00:00

Owner

The script printed seven npm publish commands for you to paste as a block. That races an unfinished npm login: the six platform publishes can fail while the browser challenge is still open, and the launcher, running last, succeeds. The launcher then sits on the registry pointing at six packages that are not there.

The v0.2.0 release came close to this. Every package did publish, but the state was unreadable for several minutes because npm view reads a local cache and reported packages as missing that had gone out a minute earlier.

scripts/release.sh <version> --publish now does the publishing itself:

It stops before the first publish when npm whoami fails, rather than after the sixth.
It publishes the six platform packages, waits for the registry to serve all six, and only then publishes the launcher.
It asks the registry over HTTP instead of using npm view, so the answer is not a stale cache.
It skips a package that is already on the registry, so a run that stops halfway can be run again.

Without --publish the script only builds, as before.

The script printed seven `npm publish` commands for you to paste as a block. That races an unfinished `npm login`: the six platform publishes can fail while the browser challenge is still open, and the launcher, running last, succeeds. The launcher then sits on the registry pointing at six packages that are not there. The v0.2.0 release came close to this. Every package did publish, but the state was unreadable for several minutes because `npm view` reads a local cache and reported packages as missing that had gone out a minute earlier. `scripts/release.sh <version> --publish` now does the publishing itself: - It stops before the first publish when `npm whoami` fails, rather than after the sixth. - It publishes the six platform packages, waits for the registry to serve all six, and only then publishes the launcher. - It asks the registry over HTTP instead of using `npm view`, so the answer is not a stale cache. - It skips a package that is already on the registry, so a run that stops halfway can be run again. Without `--publish` the script only builds, as before.

uwayss added 1 commit

2026-08-28 10:57:01 +00:00

fix(tooling): publish the release from the script 49a591f9f2

uwayss merged commit e5cd8cc62c into main

2026-08-28 10:57:40 +00:00

uwayss referenced this pull request from a commit

2026-08-28 10:57:42 +00:00

Merge pull request 'Publish the release from the script' (#12) from fix/release-script into main

uwayss deleted branch fix/release-script

2026-08-28 11:18:14 +00:00