✅ Released: agentic-jujutsu v2.3.6 - Multi-platform Native Binaries

Release Summary

Successfully released agentic-jujutsu v2.3.6 to npm with complete multi-platform support.

Package Information

• Version: 2.3.6
• npm: https://www.npmjs.com/package/agentic-jujutsu/v/2.3.6
• Git Tag: agentic-jujutsu-v2.3.6

Platform Support ✅

All 8 platforms building successfully:

• ✅ Linux x64 GNU - Standard Linux distributions
• ✅ Linux x64 MUSL - Alpine Linux x64
• ✅ Linux ARM64 GNU - ARM64 Linux (Raspberry Pi 4+)
• ✅ Linux ARM64 MUSL - Alpine Linux ARM64
• ✅ Linux ARMv7 - ARM32 devices
• ✅ macOS x64 - Intel Macs
• ✅ macOS ARM64 - Apple Silicon (M1/M2/M3)
• ✅ Windows x64 - Windows 64-bit

Key Achievements

1. Fixed macOS NAPI Linking

Created .cargo/config.toml with dynamic symbol lookup configuration to resolve NAPI linking errors on macOS and Windows.

2. Fixed Windows Build Compatibility

Added shell: bash to workflow steps to ensure Unix commands work on Windows runners.

3. Complete CI/CD Pipeline

GitHub Actions workflow now builds all 8 platforms in parallel with automated testing and artifact management.

4. Published to npm

Package successfully published and validated:

npm install agentic-jujutsu@2.3.6

Implementation Details

GitHub Actions Run: #19642825027

• All 8 platform builds: ✅ Succeeded
• Manual publish: ✅ Completed successfully

Key Files:

• packages/agentic-jujutsu/.cargo/config.toml - CREATED
• .github/workflows/build-agentic-jujutsu.yml - Updated
• packages/agentic-jujutsu/BUILD.md - Documented NPM_TOKEN requirement

Known Issues

⚠️ Automated Publishing - The workflow's publish job requires NPM_TOKEN GitHub secret. To enable automated publishing:

1. Generate npm automation token
2. Add as NPM_TOKEN secret in repository settings
3. Future tagged releases will publish all platform packages automatically

See BUILD.md for detailed instructions.

---

🤖 Generated with Claude Code

The release work is described as complete in .cargo/config.toml, .github/workflows/build-agentic-jujutsu.yml, and packages/agentic-jujutsu/BUILD.md. Start by reviewing the workflow and BUILD.md, then verify whether the NPM_TOKEN setup remains the only follow-up; this issue is done when automated publishing is documented and works for future tagged releases.