PushPals CLI v1.1.2

PushPals CLI Release Log

Release Metadata

• version: v1.1.2
• start_commit: 755dab48ef4fc622754f8ebb920b171588f5e52a
• end_commit: 5b13253f36e2d86b496f07f7a5fa59c9b9ba1df8
• commits_in_range: 1

Highlights

• Extend WorkerPal browser-validation convergence to eight targeted repair attempts while keeping non-browser and merge-conflict jobs on their configured revision limits.
• Hydrate browser repair guidance from recent e2e/log artifacts, preserving stage, selector, expected UI, prior-failure breadcrumbs, and relevant output when command output is compacted.
• Extend Docker WorkerPal job timeouts only for browser-validation jobs so the larger repair budget is not killed and restarted mid-convergence.
• Tighten OpenAI Codex WorkerPal guidance so long browser/e2e validation is delegated to ValidationGate by default, avoiding executor-only port/freeport false signals.
• Add regression coverage for browser retry scoping, dynamic Docker timeouts, artifact-backed repair packets, and prompt guidance.

Validation

• bun run cli:bundle
• bun run test:root
• git diff --check

Install

npm i -g @pushpalsdev/cli

bun install -g @pushpalsdev/cli

Artifacts

• pushpals-linux-x64
• pushpals-windows-x64.exe
• pushpals-macos-x64
• pushpals-macos-arm64
• SHA256SUMS.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 --clear cleanup is best-effort when Docker is unavailable or times out.
• Codex gpt-5.5 requires a recent Codex CLI; older Codex CLIs fall back to gpt-5.4 for 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:bundle runs 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.1.1...v1.1.2

PushPals CLI v1.1.1

PushPals CLI Release Log

Release Metadata

• version: v1.1.1
• start_commit: c15a6e9e9a0fca80a003772801f93e3ac2149e9b
• end_commit: e0ef0245a6fd5dc4a7a1a70a7fd5a2b4ea6b95bb
• commits_in_range: 1

Highlights

• Improve WorkerPal browser-validation convergence for repo-native web:e2e jobs by turning browser failures into focused repair packets with stage, selector, expected UI, prior-failure breadcrumb, and relevant output.
• Extend the browser-validation retry budget to five targeted repair attempts while keeping other ValidationGate failures on the configured retry budget.
• Hydrate Docker WorkerPal ephemeral worktrees with repo dependency artifacts such as node_modules, so Expo/Playwright smoke checks run against the same installed dependencies as the source checkout.
• Prevent sandbox artifacts, including linked node_modules, from being staged into WorkerPal commits.
• Treat browser smoke harness scripts as test harnesses without forcing app-test positive/negative assertion-balance rules onto e2e launcher scripts.
• Add bun run replay:worker-job for replaying a specific durable WorkerPal job against a running local PushPals server, making convergence bugs reproducible without running the full app workflow.
• Confirmed the previously failing SectorCommand replay passed all required validation, including default bun run web:e2e, and produced a clean PR without committing node_modules.

Validation

• bun run cli:bundle
• bun run test:root
• git diff --check

Install

npm i -g @pushpalsdev/cli

bun install -g @pushpalsdev/cli

Artifacts

• pushpals-linux-x64
• pushpals-windows-x64.exe
• pushpals-macos-x64
• pushpals-macos-arm64
• SHA256SUMS.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 --clear cleanup is best-effort when Docker is unavailable or times out.
• Codex gpt-5.5 requires a recent Codex CLI; older Codex CLIs fall back to gpt-5.4 for 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:bundle runs 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.1.0...v1.1.1

PushPals CLI v1.1.0

PushPals CLI Release Log

Release Metadata

• version: v1.1.0
• start_commit: 8fd050651899e4fc6276f20fec07cd65c933a167
• end_commit: c5074100aef593a750db9f3322ed5a6c368f838e
• commits_in_range: 1

Highlights

• Adopt the release numbering policy that patch releases roll the minor version after .99, so future releases move from vX.Y.99 to vX.(Y+1).0.
• Document the forward-only correction path for already-published patch-above-99 releases: keep the published version intact and cut the next policy-correct minor release.
• Move latest forward to v1.1.0 after the already-published v1.0.100 release.
• Confirm bun run cli:bundle produced no additional packaged runtime asset changes for this documentation-only release.

Validation

• bun run cli:bundle
• bun run test:root
• git diff --check

Install

npm i -g @pushpalsdev/cli

bun install -g @pushpalsdev/cli

Artifacts

• pushpals-linux-x64
• pushpals-windows-x64.exe
• pushpals-macos-x64
• pushpals-macos-arm64
• SHA256SUMS.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 --clear cleanup is best-effort when Docker is unavailable or times out.
• Codex gpt-5.5 requires a recent Codex CLI; older Codex CLIs fall back to gpt-5.4 for 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:bundle runs 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.100...v1.1.0

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:, and waiting 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.md validation, while the edit turn prefers focused checks instead of repeatedly running long web:e2e smoke 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.ts
• bunx tsc -p apps/workerpals/tsconfig.json --noEmit
• bun run cli:bundle
• bun run test:root
• git diff --check

Install

npm i -g @pushpalsdev/cli

bun install -g @pushpalsdev/cli

Artifacts

• pushpals-linux-x64
• pushpals-windows-x64.exe
• pushpals-macos-x64
• pushpals-macos-arm64
• SHA256SUMS.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 --clear cleanup is best-effort when Docker is unavailable or times out.
• Codex gpt-5.5 requires a recent Codex CLI; older Codex CLIs fall back to gpt-5.4 for 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:bundle runs 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

PushPals CLI v1.0.99

PushPals CLI Release Log

Release Metadata

• version: v1.0.99
• start_commit: 6bc8e40c79b5b9564d9572ff299cf044df90bf29
• end_commit: d897046ed9f911ae3cb8279891188fabe6fc5a45
• commits_in_range: 1

Highlights

• Harden WorkerPal ValidationGate command execution so browser/e2e commands that exit early while child processes keep stdio open report the real exit code and captured error output instead of looking like a 10-minute timeout.
• Default WorkerPal sandbox Node startup to IPv4-first DNS resolution and REACT_NATIVE_PACKAGER_HOSTNAME=127.0.0.1, improving Expo and React Native loopback startup behavior in Docker-backed validation.
• Classify Expo bad-port and loopback permission failures as environment blockers so WorkerPals do not burn all validation auto-revisions trying to edit unrelated application code.
• Add regression coverage for failed browser launchers that leave inherited pipes open, plus sandbox environment tests for the new Expo-friendly defaults and explicit override preservation.
• Sync packaged CLI runtime assets so the published WorkerPal sandbox includes the validation-exit and loopback-startup fixes.

Validation

• bun test tests/workerpals.validation-command-safety.test.ts tests/workerpals.sandbox-env.test.ts
• bunx tsc -p apps/workerpals/tsconfig.json --noEmit
• bun run cli:bundle
• bun run test:root
• git diff --check

Install

npm i -g @pushpalsdev/cli

bun install -g @pushpalsdev/cli

Artifacts

• pushpals-linux-x64
• pushpals-windows-x64.exe
• pushpals-macos-x64
• pushpals-macos-arm64
• SHA256SUMS.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 --clear cleanup is best-effort when Docker is unavailable or times out.
• Codex gpt-5.5 requires a recent Codex CLI; older Codex CLIs fall back to gpt-5.4 for 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:bundle runs 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.98...v1.0.99

PushPals CLI v1.0.98

PushPals CLI Release Log

Release Metadata

• version: v1.0.98
• start_commit: 5594ad8093317d153ae8f50d62f3483e75522548
• end_commit: ba2f5bcdca483221cac64d95a21393bfad3a22bf
• commits_in_range: 1

Highlights

• Teach WorkerPal ValidationGate to infer Playwright browser targets from repo e2e scripts and command flags instead of assuming every browser smoke uses bundled Chromium.
• Provision requested Playwright targets such as msedge, chrome, firefox, and webkit before running repo browser validation, fixing sandboxes where the app's smoke harness launches a browser channel.
• Track browser-runtime preflight readiness per browser target so mixed browser commands install only the missing targets.
• Improve browser preflight logs to name the exact Playwright target(s) being provisioned or failing.
• Sync packaged CLI runtime assets so the published WorkerPal sandbox includes the browser-target preflight fix.

Validation

• bun run cli:bundle
• bun run test:root
• git diff --check
• bun test tests/workerpals.sandbox-env.test.ts tests/workerpals.validation-command-safety.test.ts
• bunx tsc -p apps/workerpals/tsconfig.json --noEmit

Install

npm i -g @pushpalsdev/cli

bun install -g @pushpalsdev/cli

Artifacts

• pushpals-linux-x64
• pushpals-windows-x64.exe
• pushpals-macos-x64
• pushpals-macos-arm64
• SHA256SUMS.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 --clear cleanup is best-effort when Docker is unavailable or times out.
• Codex gpt-5.5 requires a recent Codex CLI; older Codex CLIs fall back to gpt-5.4 for 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:bundle runs 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.97...v1.0.98

PushPals CLI v1.0.97

PushPals CLI Release Log

Release Metadata

• version: v1.0.97
• start_commit: a2b1058ab9aa92f6b22ab2d366927981a9d8c228
• end_commit: a47206756b8fb55f69502cea1b47abb3fa0a3e39
• commits_in_range: 1

Highlights

• Provision WorkerPal browser validation with a stable Playwright browser cache that is shared across ephemeral job worktrees for the same repo.
• Add a ValidationGate browser runtime preflight that runs the repo-matching bunx playwright install chromium before Playwright-backed web smoke commands.
• Improve browser-validation diagnostics so missing Playwright browsers are reported as browser-runtime/tooling blockers instead of being hidden behind SIGTERM timeout summaries.
• Kill validation command process trees on timeout so Expo/Metro child processes do not linger after failed browser smoke runs.
• Sync packaged CLI runtime assets so the published WorkerPal sandbox includes the browser-runtime validation fix.

Validation

• bun run cli:bundle
• bun run test:root
• git diff --check
• bun test tests/workerpals.sandbox-env.test.ts tests/workerpals.validation-command-safety.test.ts
• bunx tsc -p apps/workerpals/tsconfig.json --noEmit

Install

npm i -g @pushpalsdev/cli

bun install -g @pushpalsdev/cli

Artifacts

• pushpals-linux-x64
• pushpals-windows-x64.exe
• pushpals-macos-x64
• pushpals-macos-arm64
• SHA256SUMS.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 --clear cleanup is best-effort when Docker is unavailable or times out.
• Codex gpt-5.5 requires a recent Codex CLI; older Codex CLIs fall back to gpt-5.4 for 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:bundle runs 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.96...v1.0.97

PushPals CLI v1.0.96

PushPals CLI Release Log

Release Metadata

• version: v1.0.96
• start_commit: bd646503dfd6ced4dab1efb3b2867ed2f2818f7d
• end_commit: fe6aec25794ab3ef668e666e7c7ff91994106af8
• commits_in_range: 3

Highlights

• Preserve Git trust config inside WorkerPal sandbox HOME so Docker-backed Codex workers can inspect mounted Linux CI worktrees after sandbox HOME/cache redirection.
• Retry the OpenAI Codex backend git-repository preflight briefly, with clearer diagnostics for transient worktree visibility/trust failures.
• Stabilize the WorkerPals Codex policy-violation E2E path by waiting for recycle deterministically and dumping worker/request diagnostics on unexpected payloads.
• Sync packaged CLI runtime assets so the published sandbox includes the WorkerPal Codex and sandbox HOME fixes.

Validation

• bun run cli:bundle
• bun run test:root
• git diff --check
• python tests/openai_codex_executor_streaming.test.py
• bun test tests/workerpals.sandbox-env.test.ts
• bun test ./tests/integration/workerpals.control-plane.e2e.ts --test-name-pattern "worker reports a codex policy violation"
• bun run test:workerpals:e2e
• GitHub Actions CLI E2E on fe6aec25794ab3ef668e666e7c7ff91994106af8: Linux Packaged CLI E2E and Linux WorkerPals Control Plane E2E passed (26330092293).

Install

npm i -g @pushpalsdev/cli

bun install -g @pushpalsdev/cli

Artifacts

• pushpals-linux-x64
• pushpals-windows-x64.exe
• pushpals-macos-x64
• pushpals-macos-arm64
• SHA256SUMS.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 --clear cleanup is best-effort when Docker is unavailable or times out.
• Codex gpt-5.5 requires a recent Codex CLI; older Codex CLIs fall back to gpt-5.4 for 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:bundle runs 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.95...v1.0.96

PushPals CLI v1.0.95

PushPals CLI Release Log

Release Metadata

• version: v1.0.95
• start_commit: 32567e810b8abc3c7342a0fdb94a0f2af722e988
• end_commit: 444394df96c8678647351877891f0145e5d284f3
• commits_in_range: 1

Highlights

• Harden Windows startup when local Git/Bun certificate verification cannot use the right Windows trust path.
• Make CLI Git commands and embedded runtime child services inherit http.sslBackend=schannel on Windows.
• Fall back from Bun GitHub release/API fetches to Windows-native paths when certificate verification fails: Git for latest tag resolution and curl.exe --ssl-no-revoke for runtime binary downloads.
• Keep Docker-backed WorkerPal startup moving after certificate fallback; local bundled CLI smoke reached ready state with WorkerPal capacity online.

Validation

• bun run cli:bundle
• bun test tests/cli.runtime-bootstrap.test.ts
• bun run test:root
• git diff --check
• Bundled Windows startup smoke: bun packages/cli/dist/pushpals-cli.js --runtime-root <temp> --runtime-tag v1.0.94 --status-once
• Source-checkout Windows startup smoke: bun scripts/pushpals-cli.ts --status-once

Install

npm i -g @pushpalsdev/cli

bun install -g @pushpalsdev/cli

Artifacts

• pushpals-linux-x64
• pushpals-windows-x64.exe
• pushpals-macos-x64
• pushpals-macos-arm64
• SHA256SUMS.txt

Breaking Changes

• None.

Known Issues

• npm publication requires the repository NPM_TOKEN secret to have publish rights for @pushpalsdev/cli under the @pushpalsdev scope.
• Docker-backed WorkerPal execution still requires Docker to be installed and running when WorkerPal auto-spawn is enabled; pushpals --clear cleanup is best-effort when Docker is unavailable or times out.
• Codex gpt-5.5 requires a recent Codex CLI; older Codex CLIs fall back to gpt-5.4 for 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:bundle runs 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.94...v1.0.95

PushPals CLI v1.0.94

PushPals CLI Release Log

Release Metadata

• version: v1.0.94
• start_commit: 099c52cd6b2faa8e73a979e37d122c75a1b32d5e
• end_commit: 78ff960251da085c67ddb7ad4d2b01d6b098939d
• commits_in_range: 4

Highlights

• Start the first RemoteBuddy autonomy tick shortly after runtime readiness, retry timed-out ideation once with a compact budget-aware prompt, and clear stale dispatch locks more aggressively on startup.
• Mask repo-local .codex sentinels before Codex CLI execution so WorkerPal ChatGPT auth can keep using the host Codex state directory.
• Treat WorkerPal planning scope metadata as review and planning hints instead of hard write boundaries; PR review remains the enforcement layer for relevance and safety.
• Avoid staging ignored runtime artifacts such as outputs, workspace, and .codex when WorkerPal creates task.execute commits.

Validation

• bun run cli:bundle
• bun run test:root
• git diff --check

Install

npm i -g @pushpalsdev/cli

bun install -g @pushpalsdev/cli

Artifacts

• pushpals-linux-x64
• pushpals-windows-x64.exe
• pushpals-macos-x64
• pushpals-macos-arm64
• SHA256SUMS.txt

Breaking Changes

• None.

Known Issues

• npm publication requires the repository NPM_TOKEN secret to have publish rights for @pushpalsdev/cli under the @pushpalsdev scope.
• Docker-backed WorkerPal execution still requires Docker to be installed and running when WorkerPal auto-spawn is enabled; pushpals --clear cleanup is best-effort when Docker is unavailable or times out.
• Codex gpt-5.5 requires a recent Codex CLI; older Codex CLIs fall back to gpt-5.4 for 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:bundle runs 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.93...v1.0.94