From eb6a64eaae19ea293a79370ea2fec2a877f84054 Mon Sep 17 00:00:00 2001 From: Janic Duplessis Date: Sat, 10 Oct 2026 21:17:31 -0400 Subject: [PATCH 1/2] docs: list the late 1.20.2 fixes in its notes --- docs/releases/1.20.2.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/docs/releases/1.20.2.md b/docs/releases/1.20.2.md index dc1cc383ba..e674f88cba 100644 --- a/docs/releases/1.20.2.md +++ b/docs/releases/1.20.2.md @@ -9,20 +9,25 @@ Stim Desktop and the Stim phone app ship through their own workflows; this relea ## Fixes - **Security:** on a checkout without its own dependencies, such as a fresh worktree or a hoisted monorepo app, `stim doctor` skips the fingerprint parity check and says why when Expo packages resolve from outside the app, or when the check would need `npx react-native config` (Android, or a project without an `ios` directory). Before, that check could run project code that doctor does not install or own. The linked-library check can still run installed Expo packages on the main checkout, as a build does. [26a22d93c](https://github.com/appandflow/stim/commit/26a22d93ca4aa16f111f4207c9677a6113efd915) +- **Security:** a cache registration whose directory is a filesystem root, or is or contains the home directory, the system temporary directory or the Stim config directory, is refused: the CLI's registration throws `cannot register this cache: ...`, `@stim-cli/core` `registerCache` ignores it, and `stim gc` never prunes or empties such a directory, reporting it as not a directory the cache owns. (`@stim-cli/core`) [a6c9ba3db](https://github.com/appandflow/stim/commit/a6c9ba3dbef2bdbeb06803b620f43caafbefe576) +- **Security:** a remote `server.update.start` from a build or device-host client refuses a release older than the running stim-server with `bad-request`, so a client with an older stim can no longer move a remote Mac back to it. `stim-server service update` run on the Mac itself is unchanged. The README and `stim guide settings` now say that a build grant is full access to the account stim-server runs as, since project code runs there unsandboxed. (`@stim-cli/server`) [fa167612a](https://github.com/appandflow/stim/commit/fa167612ad2f69cd0c851ace956cec72e8c99e15) - `stim gc` lists stale entries of the machine EAS session ledger (`~/.stim/machine/eas/sessions.json`) under "Stale EAS ledger entries": an entry whose id is not a UUID and whose absolute workspace root is missing on a mounted volume, such as ids written by a test fixture. A valid id, an existing root, or a root on an unmounted volume keeps the entry. `stim gc --delete` re-checks each entry and removes it under the ledger lock without contacting EAS. `gc --json` adds `sections.staleEasLedgerEntries` with `id` and `workspaceRoot`. [2b0e36d5b](https://github.com/appandflow/stim/commit/2b0e36d5b455bfc8efeb80ecc51c10032d5cb6df) - Every child process Stim starts has a time budget. Git calls default to 10 seconds, read-only ones run with `--no-optional-locks`, and asynchronous reads run at most six at a time. The git reads that gate `stim worktree remove` get 60 seconds; when one times out, removal refuses before any teardown with `a git safety check timed out` instead of treating a registered worktree as a plain folder. `stim gc` reports a worktree whose unpushed commits or initialized submodules could not be checked as skipped with that reason. [5f56cc4dc](https://github.com/appandflow/stim/commit/5f56cc4dc15034b47d493307f9ef9f24bdb5b14f), [bbb96cb96](https://github.com/appandflow/stim/commit/bbb96cb96bc8dee34805f5ded619fbf06dafcf0b) - `stim status --json` reports a workspace whose macOS app is running or orphaned as `stage: running`, from the app's build end when no Metro supervisor runs. Stim Desktop and the phone app now show the stage, app presence and git chip that stim reports instead of computing their own. (`@stim-cli/core`) [14c46bf48](https://github.com/appandflow/stim/commit/14c46bf488c04355b3524070f1de22f06b006522) +- stim-server build uploads: `build.sync` fails with `build-busy` while the worker root's volume has less than 10 GiB free and with `limit-exceeded` once one manifest's sizes add up to more than 20 GiB, and a blob that would leave the volume under 10 GiB free closes the connection with 4400. When a client's build ends and no other build of that client runs, the server deletes the client's blobs that no checkout and no open manifest uses; blob pruning stops without deleting anything when a mirror record cannot be read. A revoked build client's directory under the worker root is deleted once its builds end, unless the client has not connected since the server started. (`@stim-cli/server`) [fdae5685c](https://github.com/appandflow/stim/commit/fdae5685ca33fcf81d6cbb4f9ee04d604c2a1b4c), [f87b6115b](https://github.com/appandflow/stim/commit/f87b6115ba7b80bd43c10e2e3d4230e5af31c74d) +- `stim macos` waits up to 20 seconds for macOS LaunchServices to list the launched app before it returns, so `agent-device open` attaches to it instead of starting a second copy without Stim's launch arguments. If the app is still unlisted, it warns and returns; a `--remote` launch skips the wait. `stim guide macos` and the website describe the wait instead of the manual `lsappinfo` loop. [0d5bbf727](https://github.com/appandflow/stim/commit/0d5bbf727cf942b99a531ddde6eb0d3f4057ec75), [a3a4c9fd6](https://github.com/appandflow/stim/commit/a3a4c9fd6e2f8d0dac2ead69517ef15334e31c06) +- Relaunching an Android app whose process state cannot be read launches with `am start -S`, which force-stops the app as part of the start, so a slow `adb` no longer refuses the relaunch; an app without a launcher activity gets a best-effort `am force-stop` before `monkey`. A known running pid still gets a separate force-stop. [313f2c1a0](https://github.com/appandflow/stim/commit/313f2c1a089937a3f5ab4135475677632f650b43) +- A hosted install waits 355 seconds instead of 300, covering the host's install deadline plus its settle bound; the client's hosted waits now derive from the server's limits in `@stim-cli/core`. [b5c6b9d86](https://github.com/appandflow/stim/commit/b5c6b9d86a44f6ffa620b24ddbefa2caae56a1ee) - The Release workflow refuses to publish a tag whose commit is not on `main`. This changes the release process, not a package. [2bbf06e69](https://github.com/appandflow/stim/commit/2bbf06e694d76f3d7703c943a3fd4e4ff6da9215) ## Docs - `stim guide tutorial run` has the agent check the change by picking a size (`size-s`, `size-m` or `size-l`) instead of typing a name. [e50e7b25b](https://github.com/appandflow/stim/commit/e50e7b25b8d9b794006521a677b1385350f26b56) -- `stim guide macos` has the agent wait until `lsappinfo` lists the app's recorded pid before `agent-device open`, because `stim macos` can return before macOS LaunchServices lists the app, and opening it then starts a second copy without Stim's launch arguments. [a3a4c9fd6](https://github.com/appandflow/stim/commit/a3a4c9fd6e2f8d0dac2ead69517ef15334e31c06) ## QA The maintainer approved this release on 2026-10-10. Pre-tag QA is omitted, as with 1.18.0 to 1.20.1. This deviates from RELEASE.md section 3, which has no waiver for a stable version. -Omitted before the tag, all eight rows of the matrix (`node scripts/release-qa-matrix.mjs v1.20.1`; 193 changed paths, 50 mapped to a row, 0 unclassified): loop, logs, caches, real-repository, remote-provider, release-build, android-flavor and launch-evidence, plus the native suites `run-native-e2e.mjs` and `run-cache-e2e.mjs`. +Omitted before the tag, all eight rows of the matrix (`node scripts/release-qa-matrix.mjs v1.20.1`; 250 changed paths, 87 mapped to a row, 0 unclassified): loop, logs, caches, real-repository, remote-provider, release-build, android-flavor and launch-evidence, plus the native suites `run-native-e2e.mjs` and `run-cache-e2e.mjs`. Run before the version commit: `format:check`, `lint`, `build`, `typecheck`, `knip`, `release:prep --check`, CLI version/help/guide, `licenses:check` in `apps/mobile`, and pnpm tarball inspection of the seven packages. Not run locally, left to CI: `pnpm test`, `test:e2e`, `test:runtime` and `test:compat`. Run after push: exact-commit CI, including the full Windows job, and the Release workflow's own gates, including its new tag-on-main check. From 96c8273d26427c7adb78c6226168fe7c64f58de5 Mon Sep 17 00:00:00 2001 From: Janic Duplessis Date: Sat, 10 Oct 2026 21:23:15 -0400 Subject: [PATCH 2/2] docs: correct the Android relaunch line in the 1.20.2 notes --- docs/releases/1.20.2.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/releases/1.20.2.md b/docs/releases/1.20.2.md index e674f88cba..e771018ff5 100644 --- a/docs/releases/1.20.2.md +++ b/docs/releases/1.20.2.md @@ -16,7 +16,7 @@ Stim Desktop and the Stim phone app ship through their own workflows; this relea - `stim status --json` reports a workspace whose macOS app is running or orphaned as `stage: running`, from the app's build end when no Metro supervisor runs. Stim Desktop and the phone app now show the stage, app presence and git chip that stim reports instead of computing their own. (`@stim-cli/core`) [14c46bf48](https://github.com/appandflow/stim/commit/14c46bf488c04355b3524070f1de22f06b006522) - stim-server build uploads: `build.sync` fails with `build-busy` while the worker root's volume has less than 10 GiB free and with `limit-exceeded` once one manifest's sizes add up to more than 20 GiB, and a blob that would leave the volume under 10 GiB free closes the connection with 4400. When a client's build ends and no other build of that client runs, the server deletes the client's blobs that no checkout and no open manifest uses; blob pruning stops without deleting anything when a mirror record cannot be read. A revoked build client's directory under the worker root is deleted once its builds end, unless the client has not connected since the server started. (`@stim-cli/server`) [fdae5685c](https://github.com/appandflow/stim/commit/fdae5685ca33fcf81d6cbb4f9ee04d604c2a1b4c), [f87b6115b](https://github.com/appandflow/stim/commit/f87b6115ba7b80bd43c10e2e3d4230e5af31c74d) - `stim macos` waits up to 20 seconds for macOS LaunchServices to list the launched app before it returns, so `agent-device open` attaches to it instead of starting a second copy without Stim's launch arguments. If the app is still unlisted, it warns and returns; a `--remote` launch skips the wait. `stim guide macos` and the website describe the wait instead of the manual `lsappinfo` loop. [0d5bbf727](https://github.com/appandflow/stim/commit/0d5bbf727cf942b99a531ddde6eb0d3f4057ec75), [a3a4c9fd6](https://github.com/appandflow/stim/commit/a3a4c9fd6e2f8d0dac2ead69517ef15334e31c06) -- Relaunching an Android app whose process state cannot be read launches with `am start -S`, which force-stops the app as part of the start, so a slow `adb` no longer refuses the relaunch; an app without a launcher activity gets a best-effort `am force-stop` before `monkey`. A known running pid still gets a separate force-stop. [313f2c1a0](https://github.com/appandflow/stim/commit/313f2c1a089937a3f5ab4135475677632f650b43) +- Relaunching an Android app whose process state cannot be read launches with `am start -S`, which force-stops the app as part of the start. Before, Stim launched without stopping it, so a running app could keep its old process and bundle. An app without a launcher activity gets a best-effort `am force-stop` before `monkey`, and a known running pid still gets a separate force-stop that refuses the launch when it fails. [313f2c1a0](https://github.com/appandflow/stim/commit/313f2c1a089937a3f5ab4135475677632f650b43) - A hosted install waits 355 seconds instead of 300, covering the host's install deadline plus its settle bound; the client's hosted waits now derive from the server's limits in `@stim-cli/core`. [b5c6b9d86](https://github.com/appandflow/stim/commit/b5c6b9d86a44f6ffa620b24ddbefa2caae56a1ee) - The Release workflow refuses to publish a tag whose commit is not on `main`. This changes the release process, not a package. [2bbf06e69](https://github.com/appandflow/stim/commit/2bbf06e694d76f3d7703c943a3fd4e4ff6da9215)