Repository navigation
Scriptorium v2.0.0
Scriptorium 2.0.0 installs and develops with pnpm 11 (the package pins 11.28.8) instead of npm. The toolchain also moves to TypeScript 7, oxlint and Prettier, and a single pnpm validate runs every check.
When an ended or orphaned run keeps its claim because its pull request is still open, the factory now posts one notice saying so, instead of holding the issue silently. Repositories can customize the wording with the optional comments.awaitingMerge template.
The sandbox image and the host installation keep pnpm's content store outside the checkout, so runs never leave a .pnpm-store/ in the working tree.
Impact
Host installation changes. A release tree has pnpm-lock.yaml and no package-lock.json, so an installer that runs npm ci can't prepare it. The host configuration schema and the factory configuration schema (version 1) are unchanged. Existing repository configurations keep loading, and comments.awaitingMerge is optional.
Migration
In this order:
- Provide pnpm 11.28.8 on the host's operational
PATH. - Install production dependencies with
pnpm install --prod --frozen-lockfile --ignore-scripts, with a writable store directory outside the release tree. - Let the updater admit the 2.x stream deliberately; hosts stay on their pinned major otherwise.
- Only then let it take 2.0.0. Keep the retained 1.x tree for rollback.
See the host guide and the factory configuration reference.
Verification
Release commit 008d3594c249e74b4fa8b21488b6bb124c602228, from release pull request #59 (reviewed head 69aadecb2d0a1e502af36d8bbe8201b17424a4fd; the trees are identical). The annotated tag scriptorium-v2.0.0 peels to the release commit. The release is neither a draft nor a prerelease and appears in the release list. Required CI passed on Node.js 24 and 26, along with the sandbox image and PR metadata checks, and Codex found no issues. Node.js 24's test job needed re-runs for a missing runner Docker daemon and an order-dependent test, tracked as #60.