Repository navigation
PushPals CLI v1.0.100
PushPals CLI Release Log
Release Metadata
- version:
v1.0.100 - start_commit:
250de11af911e745d2e656acff58821f7ab7e427 - end_commit:
d0cfda05d56a8e7f6afd85801e5a32b3692faf73 - commits_in_range:
2
Highlights
- Stop leaked browser/e2e validation process trees after a captured fatal browser failure goes idle, so WorkerPal jobs preserve the actionable failure instead of burning the full ValidationGate timeout.
- Recognize Playwright locator failures such as
locator.waitFor: Timeout ... exceeded,Call log:, andwaiting for getByTestId(...)as browser smoke failures that should fail fast. - Keep browser/e2e validation output useful by extracting the specific Playwright, network, and browser launch failure lines into validation digests.
- Clarify WorkerPal Codex execution guidance so the deterministic ValidationGate owns repo-required
vision.mdvalidation, while the edit turn prefers focused checks instead of repeatedly running longweb:e2esmoke commands. - Sync packaged CLI runtime and prompt assets so published WorkerPal sandboxes receive the browser-validation watchdog and prompt updates.
Validation
bun test tests/workerpals.validation-command-safety.test.tsbunx tsc -p apps/workerpals/tsconfig.json --noEmitbun run cli:bundlebun run test:rootgit diff --check
Install
npm i -g @pushpalsdev/clibun install -g @pushpalsdev/cliArtifacts
pushpals-linux-x64pushpals-windows-x64.exepushpals-macos-x64pushpals-macos-arm64SHA256SUMS.txt
Breaking Changes
- None.
Known Issues
- Docker-backed WorkerPal execution still requires Docker to be installed and running when WorkerPal auto-spawn is enabled;
pushpals --clearcleanup is best-effort when Docker is unavailable or times out. - Codex
gpt-5.5requires a recent Codex CLI; older Codex CLIs fall back togpt-5.4for WorkerPal and RemoteBuddy Codex execution when they report model incompatibility. - GitHub contribution credit for WorkerPal commits requires the configured commit email to be associated with the target GitHub account.
- Native WSL source-tree
cli:bundleruns can still hang in the Expo monitor export path when building from a Windows-mounted checkout under/mnt/c/...; the published CLI package cold-start path is covered separately.
Full Changelog: v1.0.99...v1.0.100