Playtestr v0.4.0-rc.1 release notes#

Published 25 September 2026 from frozen runner source f6ffeb76a7ec3b826052690ab53071dcdf0e565f. The three archives below retain their qualified hashes and have not been replaced.

Verified installation: pin the setup action to Wyrcan-io/playtestr/setup-playtestr@1c03904075512e67f53b0c94a13daa17f0383f1d and select v0.4.0-rc.1. The published-install matrix and public-byte/upgrade matrix passed on Windows amd64, Linux amd64, and macOS arm64. Direct archives remain available below.

This prerelease adds opt-in specification version 2 workspaces: every run can copy a bounded reviewed fixture and receive managed home and temporary directories. V2 and mixed suites emit report version 2 so setup, primary test, and cleanup outcomes stay distinct. All-v1 suites retain report v1 and existing v1 terminal/action semantics.

It also includes exact-version setup-action source, stronger transactional installation failure handling, complete v1/v2 offline HTML rendering, three copyable recipes, and native archive/terminal hardening. The qualified corpus contains 120 workflows across 15 pinned applications; that is technical operator evidence, not maintainer endorsement or independent adoption.

Downloads#

Choose exactly one archive and verify it against checksums-v0.4.0-rc.1.txt .

Archive fallback requires no installer: extract the matching archive, verify the executable hash in the candidate manifest , run playtestr version, and put its directory on PATH only after verification.

The first proposed action revision expected a per-archive checksum asset and failed safely against this release’s aggregate manifest. The immutable repair supports both contracts; the failed run and repair are preserved in the R6 publication and verification record .

Compatibility and limits#

• Specs: v1 and v2. V2 requires workspace; no v1 behavior changes implicitly.
• Reports: all-v1 suites write v1; v2 or mixed suites write v2. The candidate’s HTML renderer reads both.
• Previous v0.3.0-rc.1 passes the reviewed v1 menu flow and diagnoses its intentional mismatch; it does not support v2 workspaces.
• Targets execute with the user’s permissions. Playtestr is not a sandbox.
• Compatibility is scoped by exact project/version/host/workflow evidence. No universal framework, Unicode, accessibility, or zero-flakiness claim is made.
• Target-rendered secrets can appear in reports and snapshots. Review fixtures and retained evidence; automatic redaction is not promised.

See the migration and rollback guide and qualification record .

View source ↗ · Suggest an edit ↗