openclaw/mcporter v0.10.1 on GitHub

Changes

Fixed Bun-compiled standalone macOS binaries so mcporter generate-cli --compile works from an empty directory, even when there is no local package.json or node_modules tree.
generate-cli --compile now stages the matching published mcporter package dependencies when bundled dependencies cannot be linked or copied from the local package tree.
The Bun compile step now runs from the staging directory, so generated CLI builds resolve mcporter, commander, and related dependencies from the same directory that contains the generated artifact.
Added a clearer failure message for standalone development binaries that cannot resolve published bundler dependencies.

Added an opt-in standalone Bun release-binary regression smoke behind MCPORTER_STANDALONE_BINARY_TEST=1.
The smoke builds dist-bun/mcporter, packs the current package, runs generate-cli --compile from an empty temp directory, and verifies the compiled CLI help output.

Clarified that the Homebrew formula should install the npm .tgz, not the standalone Bun macOS tarball, because generated CLI compilation needs the installed package tree.
Documented the Homebrew release verification flow: update the tap URL/SHA, use --min-release-age=0, refresh tap README callouts, run brew reinstall, brew test, and run an empty-directory compile smoke with /opt/homebrew/bin/mcporter.
Documented npm and npx post-release verification, plus optional repeat verification on another Mac.

Started the next development cycle after v0.10.0 with a fresh Unreleased changelog stub.

mcporter-macos-arm64-v0.10.1.tar.gz
- SHA256: 17451e9fd0cba13c4c506d43a3574f1cf8c707d9076aa1d22381d958199e0e1f
mcporter-0.10.1.tgz
- SHA1: 918af2d239a8e27292c9621bae965e07578bdb1e
- SHA256: efef969838b18df0bcbc3b5fe3d4a7057a96e99c46a3f25e2deb0dfd7afee1d3
Uploaded checksum files:
- mcporter-macos-arm64-v0.10.1.tar.gz.sha256
- mcporter-0.10.1.tgz.sha1
- mcporter-0.10.1.tgz.sha256