Skip to content

Castwright v1.12.3

Choose a tag to compare

View all tags
@github-actions github-actions released this 11 Jul 06:07
v1.12.3
36cc956

A patch release: the one-click Pinokio install now works end to end. v1.12.3 consolidates the run of installer fixes since v1.12.0 — it supersedes and replaces the v1.12.1 and v1.12.2 patches. A fresh Pinokio Download → Install → Start now goes all the way through: the Install button fires the installer, every setup step runs from the right directory, and the server starts fully configured from its own server/.env.

Migration: this release relocates the launcher directory (pinokio/ → pinokio-scripts/). Pinokio's in-app Update cannot cross a launcher-dir rename — an existing v1.12.x install's frozen resolve-release.js guards the old path and aborts. Existing Pinokio users must reinstall fresh, not Update. (Blast radius is minimal: the app was delisted across the 1.12.x installer patches, so few installs exist; the v1.12.1/v1.12.2 releases are deleted at cut.)

🚀 Onboarding

  • The Pinokio Install button now auto-fires the installer on first activation. The launcher scripts lived under a folder named pinokio/ — a name the current Pinokio runtime reserves internally — so the download-screen Install button rendered but never triggered install.js (running it by hand from inside the app still worked, which is why installs completed when triggered manually but looked broken to first-time users). Renamed the launcher subtree to pinokio-scripts/, bumped its script schema version 1.0 → 7.0 to match every shipping Pinokio app, and added structural tests that load the real launcher and assert the folder isn't a reserved name, the schema version is current, and every menu action resolves to a real script. (#1529)
  • The installer's own setup steps now run from the app root, not the launcher folder (was v1.12.1). Every shell.run/fs.rm step defaulted its working directory to the script's own launcher folder rather than the app root, so the very first setup step (the conda env) resolved one directory too deep and failed before anything installed. Each step now sets path: '..' to reach the app root. (#1508, #1509)
  • A Pinokio-launched server no longer boots on bare defaults (was v1.12.2). Once install ran, Start launched the server from the app's top folder instead of its server/ folder, so it couldn't find its own .env — workspace location, worker counts, GPU memory budget, analyzer settings — and quietly fell back to defaults. It now launches from server/ (matching how the desktop app has always started it), so a Pinokio install comes up with its real settings from the first run. (#1513, #1514)

Full changelog: v1.12.0...v1.12.3

Assets 8
Loading