Follow @plannotator on X for updates
Missed recent releases?
| Release | Highlights |
|---|---|
| v0.17.8 | Configurable default diff type, close button for sessions, annotate data loss fix, markdown rendering polish |
| v0.17.7 | Fix "fetch did not return a Response" error in OpenCode web/serve modes |
| v0.17.6 | Bun.serve error handlers for diagnostic 500 responses, install.cmd cache fix |
| v0.17.5 | Fix VCS detection crash when p4 not installed, install script cache path fix |
| v0.17.4 | Vault browser merged into Files tab, Kanagawa themes, Pi idle session tool fix |
| v0.17.3 | Sticky lane repo/branch badge overflow fix |
| v0.17.2 | Supply-chain hardening, sticky toolstrip and badges, overlay scrollbars, external annotation highlighting, Conventional Comments |
| v0.17.1 | Pi PR review parity, parseRemoteUrl rewrite, cross-repo clone fixes, diff viewer flash fix |
| v0.17.0 | AI code review agents, token-level annotation, merge-base diffs |
| v0.17.9 | Gemini CLI plan review, install script skills directory fix |
| v0.16.6 | Perforce support, Pi shared event API, suggested code prefill, file tree expand fix |
| v0.16.5 | Resize handle scrollbar fix, VS Code Marketplace publish |
What's New in v0.17.9
v0.17.9 is a hotfix for a macOS binary signing regression introduced by Bun 1.3.12.
Fix: macOS Binary Killed on Launch (Bun 1.3.12 Regression)
Users on macOS Sequoia reported that the v0.17.8 binary was killed immediately on launch with no output — zsh: killed ~/.local/bin/plannotator. The binary was a valid Mach-O executable but had no code signature at all, causing macOS to SIGKILL it before it could run.
The regression was introduced by Bun 1.3.12. The release workflow uses bun-version: latest, so v0.17.8's build picked up 1.3.12 while v0.17.7 had been built with 1.3.11. Bun 1.3.11 injects an ad-hoc linker signature into cross-compiled macOS binaries; 1.3.12 does not. macOS Sequoia enforces stricter unsigned binary restrictions and kills them outright.
The fix pins bun-version to 1.3.11 across all three workflow jobs (test, build, npm-publish) until the upstream Bun issue is resolved.
If you're on v0.17.8 and can't wait for the update, the workaround is to apply the signature manually:
codesign --sign - --force ~/.local/bin/plannotator- Fixes #541, reported by @aviadshiber
Install / Update
macOS / Linux:
curl -fsSL https://plannotator.ai/install.sh | bashWindows PowerShell:
irm https://plannotator.ai/install.ps1 | iexPin a specific version:
curl -fsSL https://plannotator.ai/install.sh | bash -s -- --version v0.17.9Claude Code Plugin: Run /plugin in Claude Code, find plannotator, and click "Update now".
Copilot CLI:
/plugin marketplace add backnotprop/plannotator
/plugin install plannotator-copilot@plannotator
Gemini CLI: The install script auto-detects ~/.gemini and configures hooks, policy, and slash commands.
OpenCode: Clear cache and restart:
rm -rf ~/.cache/opencode/packages/@plannotator ~/.bun/install/cache/@plannotatorThen in opencode.json:
{
"plugin": ["@plannotator/opencode@latest"]
}Pi: Install or update the extension:
pi install npm:@plannotator/pi-extensionVS Code Extension: Install from the VS Code Marketplace.
What's Changed
- fix: pin Bun to 1.3.11 to fix macOS binary codesign regression (Bun 1.3.12) by @backnotprop
Community
@aviadshiber reported the issue in #541 with a full diagnostic — binary path, SHA256, codesign output, and the workaround — which made the root cause straightforward to identify and fix.
Full Changelog: v0.17.8...v0.17.9
