PushPals CLI v1.0.62

PushPals CLI Release Log

Release Metadata

• version: v1.0.62
• start_commit: 4b50ff571db53ad548ff8b87921ec383e74de86d
• end_commit: a988ec892e2e21fc6f5a880307f83c2fdbdd2954
• commits_in_range: 1

Highlights

• Scrub transient untracked .codex artifacts out of WorkerPal job worktrees before rebase-based branch sync so successful task commits do not get blocked by Git checkout protection during finalization.
• Keep Codex state outside repo worktrees even when PUSHPALS_OPENAI_CODEX_HOST_CODEX_HOME is set to a relative path, and log the fallback to the user home Codex directory for visibility.
• Move command-router wrapper policy guidance into [prompts/workerpals/openai_codex_command_router_policy.md] so the base guidance, recovery message, and rejection detail stay editable in one prompt-managed place while preserving mirrored runtime behavior.

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

• 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 and passes on native WSL Bun.
• Per-app tsc --noEmit still trips over the existing unrelated shared-config typing issue in packages/shared/src/config.ts; release validation for this change relied on targeted WorkerPals regressions and end-to-end suites instead.

Full Changelog: v1.0.61...v1.0.62

PushPals CLI v1.0.61

PushPals CLI Release Log

Release Metadata

• version: v1.0.61
• start_commit: d6a3750cc903aebff16de37df09d0b40179799f8
• end_commit: 93c51bc177e9e36177bc51b2edfc0639ea267fe7
• commits_in_range: 1

Highlights

• Preserve successful local WorkerPal task commits as a distinct publish_blocked terminal state when final branch sync or push fails, instead of misreporting them as generic commit-creation failures.
• Surface branch-finalization diagnostics through the worker, Docker job runner, server API, and dashboard so stuck publish races now report the exact sync/push failure along with the saved hidden ref and commit SHA.
• Harden rebase-based branch sync to resolve add/add and delete-vs-modify conflicts in worker favor without accidentally staging unrelated untracked files, and add regression coverage for those finalization races.

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

• 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 and passes on native WSL Bun.
• Per-app tsc --noEmit still trips over the existing unrelated shared-config typing issue in packages/shared/src/config.ts; release validation for this change relied on WorkerPals/server compile checks and targeted end-to-end suites instead.

Full Changelog: v1.0.60...v1.0.61

PushPals CLI v1.0.60

PushPals CLI Release Log

Release Metadata

• version: v1.0.60
• start_commit: 3cc70920dee7751184ebfb7958d0d20ee6dece30
• end_commit: a8f3dcff239cae2633c34f42b32538c6c56f24a8
• commits_in_range: 1

Highlights

• Add a real installed-package smoke runner that verifies the published @pushpalsdev/cli package cold-starts the embedded runtime, survives pushpals --clear, and reaches --status-once readiness on both Windows and Linux.
• Extend packaged CLI end-to-end coverage to install the freshly packed CLI tarball into an isolated global Bun prefix and boot the installed pushpals entrypoint instead of only testing the source-tree bundle.
• Wire post-publish release canaries into the release workflow so every tagged release now validates the actual npm package install path on both windows-2022 and ubuntu-latest after publish, closing the gap that let installed-package startup regressions escape earlier releases.

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

• 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 and passes on native WSL Bun.

Full Changelog: v1.0.59...v1.0.60

PushPals CLI v1.0.59

PushPals CLI Release Log

Release Metadata

• version: v1.0.59
• start_commit: cec8e75eb0c4807e24184f89621bd91b2a50fa93
• end_commit: 7b1b22ec80928c60d13f9da736264ce7b5393d27
• commits_in_range: 4

Highlights

• Recover Windows embedded CLI startup when the standalone RemoteBuddy runtime crashes with a Bun panic by swapping the managed service in place and rerunning a prebundled fallback asset under Bun instead of aborting the whole session.
• Ship the bundled RemoteBuddy fallback JS inside the CLI runtime asset set so the recovery path works from the extracted runtime tree without requiring a workspace install or bun install.
• Harden Windows runtime asset sync against transient EBUSY cleanup races during bundle and test cycles, and add forced-crash CLI E2E coverage for the exact fallback path on both Windows and WSL Ubuntu.
• Stabilize the hosted Windows release smoke by using deterministic OpenAI Codex API-key auth and accepting a logged WorkerPal warmup attempt with known Docker limitations as a valid runner outcome while still proving RemoteBuddy and server startup health.

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 end-to-end coverage and hosted Windows smoke still depend on the underlying Docker daemon being healthy; when Docker Desktop itself is wedged, real-Docker integration runs will stall or downgrade until Docker is restarted.

Full Changelog: v1.0.58...v1.0.59

PushPals CLI v1.0.57

PushPals CLI Release Log

Release Metadata

• version: v1.0.57
• start_commit: 80366bb5fea608b22de7227f0823cb3c33b4a823
• end_commit: ccd327875e68d008291e368bfada30f7f5e63082
• commits_in_range: 2

Highlights

• Fail orphaned claimed jobs as soon as the server can prove a worker heartbeat has dropped ownership, instead of leaving the job stuck in claimed until the stale-claim watchdog fires minutes later.
• Add an explicit abandoned recovery state for retry-safe lost claims and preserve successor lineage through resumeOfJobId, attempt tracking, and params.resume metadata instead of flattening every recovery into a hard failure.
• Auto-requeue only retry-safe work such as warmup.execute, while keeping non-idempotent task.execute jobs as hard failures with clearer diagnostics and updated queue-health telemetry.
• Update server and dashboard surfaces to expose abandoned jobs in queue snapshots, lifecycle timing, and failure-rate style health signals, with regression coverage for both heartbeat-mismatch and stale-watchdog recovery paths.

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

• task.execute resume metadata is preserved for future continuation logic, but non-idempotent abandoned jobs still restart via explicit retry rather than automatic in-place continuation.

Full Changelog: v1.0.56...v1.0.57

PushPals CLI v1.0.56

PushPals CLI Release Log

Release Metadata

• version: v1.0.56
• start_commit: 2ffc0781fde084d73580b9d09b170e6719073ffd
• end_commit: e7bf8cfeea47ea7564fc9d1072afc76992ef2129
• commits_in_range: 1

Highlights

• Continue through chained merge-conflict rebases when git rebase --continue advances into the next conflicted commit instead of treating that forward progress as a terminal failure.
• Rerun the merge-conflict resolver on updated paused-rebase sandbox state with a bounded pass count so multi-commit conflict chains can finish without risking infinite loops.
• Revalidate WorkerPals merge-conflict policy and control-plane execution paths before release.

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

• None.

Full Changelog: v1.0.55...v1.0.56

PushPals CLI v1.0.55

PushPals CLI Release Log

Release Metadata

• version: v1.0.55
• start_commit: a0f6d18600f9880e5bb91f2961e783784c5b66f3
• end_commit: 3e94b41e61a9c4a26d643bf9528d4b7303453f29
• commits_in_range: 1

Highlights

• Harden cross-platform CLI Docker timeout recovery coverage so the timed-out inspect rebuild path still triggers when Docker inspect command shape changes between environments.
• Pin the merge-conflict WorkerPals end-to-end lane to deterministic Codex API-key auth so Linux and Windows CI no longer depend on interactive login state inside Docker-backed test runs.
• Revalidate the packaged CLI and WorkerPals control-plane E2E suites on both Windows and Linux to reduce stuck-job regressions before release.

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

• None.

Full Changelog: v1.0.54...v1.0.55

PushPals CLI v1.0.54

PushPals CLI Release Log

Release Metadata

• version: v1.0.54
• start_commit: 0790d2c147334f959146ee5dfdbd7046ac6b6fa9
• end_commit: 009ed9e7ad5b5096b7616df36438191dd475a217
• commits_in_range: 3

Highlights

• Fix merge-conflict quality gating so prepared conflict paths still count after the sandbox rebase auto-continues, and classify missing dependencies/imports as repo blockers instead of wasting revision retries.
• Relax the test assertion-balance heuristic after focused validation really passes, preventing false failures when negative coverage is expressed through invariants like unchanged counts or .not assertions.
• Soft-pass exhausted quality revisions for publishable review-fix and merge-conflict PR updates so WorkerPals still pushes the revision while keeping unfinished rebases and real repo/environment blockers as hard failures.

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

• None.

Full Changelog: v1.0.53...v1.0.54

PushPals CLI v1.0.53

PushPals CLI Release Log

Release Metadata

• version: v1.0.53
• start_commit: 3c74ec86ab8f29f420d2387588a7dc796746e921
• end_commit: 00c601ea5d30378f34f8b2edd28a638e6b83ed1f
• commits_in_range: 1

Highlights

• Fix RemoteBuddy worker startup so a freshly spawned WorkerPal that comes online already busy is treated as healthy instead of being killed as "not ready."
• Prevent queued work from being stranded behind false startup timeouts that later surface as stale-claim job failures.
• Add regression coverage for the busy-on-startup worker path so startup readiness stays separate from idle-capacity selection.

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

• None.

Release Checklist

• Confirm release_log.md content before tagging.
• Tag and push: git tag v1.0.53 && git push origin v1.0.53.

Full Changelog: v1.0.52...v1.0.53

PushPals CLI v1.0.52

PushPals CLI Release Log

Release Metadata

• version: v1.0.52
• start_commit: 395a17a37919fb6574dc04b4f234b4e850b53f63
• end_commit: dc40f0a40646eb4728563f4c55640133990084dc
• commits_in_range: 2

Highlights

• Extend pushpals --clear to remove PushPals-owned stale Docker artifacts, including repo-scoped warm containers and the local WorkerPal sandbox image tag.
• Standardize the shared Python worker logger contract so backend recovery paths can safely use Python-style logger methods without wrapper crashes.
• Auto-stage resolved merge-conflict files and continue prepared rebases when no conflict markers remain, while still failing fast on truly unresolved conflicts.

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

• None.