Skip to content

PushPals CLI v1.1.28

Choose a tag to compare

View all tags
@github-actions github-actions released this 09 Jun 07:50
· 8 commits to main since this release
v1.1.28
e578e9a

PushPals CLI Release Log

Release Metadata

  • version: v1.1.28
  • start_commit: ee9762a30878f542824481f3bf0136efe042ee3d
  • end_commit: e29ff2032ec3f19d2e3f9925ba504cb4660c1037
  • commits_in_range: 4

Highlights

  • Fall back from Docker-backed WorkerPal spawning to a direct isolated-worktree WorkerPal after a Docker Codex startup stall, so later jobs can make publishable progress instead of repeating the same stalled container path.
  • Propagate Codex startup-stall cooldowns through the Docker job runner with a distinct worker exit code, preserving the 10-minute cooldown signal while allowing RemoteBuddy to switch execution backends.
  • Keep repeated startup stalls classified as infrastructure/startup failures instead of no-publishable trajectory failures, improving diagnostics and rollout-coach decisions.
  • Stabilize the git-heavy merge-conflict release checks with explicit timeout headroom under full-suite Windows load.
  • Ship the refreshed packaged CLI runtime fallback assets generated by bun run cli:bundle.

Validation

  • bun run cli:bundle
  • bun test tests/workerpals.merge-conflict-job.test.ts
  • 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.
  • Active runtimes that were started from v1.1.27 or earlier must be restarted after installing this release before the new Docker Codex startup-stall fallback behavior takes effect.
  • Docker-backed WorkerPal execution still uses the first stalled Docker Codex startup as the signal to switch future WorkerPal spawns to direct isolated-worktree execution; the first affected job may fail as the canary that activates fallback.
  • 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.
  • User-local runtime/configs/local.toml overrides can preserve older runtime defaults during manual smoke testing; use pushpals --clear or remove the local override to pick up new packaged defaults.
  • Some Windows Git installations may need Schannel certificate handling for remote operations, for example git -c http.sslBackend=schannel fetch origin.

Full Changelog: v1.1.27...v1.1.28

Assets 27
Loading