binzo-cli 0.0.1 → 0.0.3

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Binzo contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -5,12 +5,12 @@ Your tools, straight from the source. Install command-line tools from release do
 Install with npm (Node.js 20 or newer; Bun is not required):
 
 ```sh
-npm install --global binzo
+npm install --global binzo-cli
 ```
 
 npm selects the binary package for your OS, architecture, and Linux libc. A one-time install script places that executable at npm’s command path. Running `binzo` then starts the native executable directly, without a Node launcher or wrapper process.
 
-The `binzo` package contains the install script, README, and package metadata; each platform package contains its executable, README, and package metadata. Application source code, tests, and development tools are excluded from the published payload.
+The `binzo-cli` package contains the install script, README, license, and package metadata; each platform package contains its executable, README, license, and package metadata. Application source code, tests, and development tools are excluded from the published payload.
 
 ```sh
 binzo add aaif-goose/goose
@@ -173,6 +173,16 @@ The tag supplies the binary’s version, with a leading `v` removed from numeric
 
 Publishing uses the built-in `GITHUB_TOKEN`; no additional secret is needed. Failed runs can be rerun from GitHub Actions: an unfinished draft is resumed, and an already published release is left intact.
 
+### Rebuilding a release from main
+
+To use the current `main` branch for an existing release tag, open **Actions → Release → Run workflow**, choose **main**, and enter the tag (for example, `v0.0.2`). Or run:
+
+```sh
+gh workflow run release.yml --ref main -f tag=v0.0.2
+```
+
+The manual trigger must first be committed and pushed to `main`. It checks and builds one fixed commit from `main`, uses the supplied tag as the binary version, and creates or updates that tag’s GitHub Release. Existing mutable release assets are replaced. The release notes record the actual build commit; the Git tag itself is not moved.
+
 ### Publishing to npm manually
 
 npm publishing is separate from GitHub Actions. The eight binary packages live in `npm/` as npm workspaces. Keep their versions and the root package’s exact `optionalDependencies` versions aligned with the root `version`.
@@ -186,7 +196,7 @@ npm publish --workspaces
 npm publish
 ```
 
-Each binary package’s `prepack` command builds its executable directly with Bun before packing or publishing. Publishing uses your local npm authentication and requires access to `binzo` and the eight unscoped `binzo-*` names. For prereleases, add `--tag next` to both publish commands.
+Each binary package’s `prepack` command builds its executable directly with Bun before packing or publishing. Publishing uses your local npm authentication and requires access to `binzo-cli` and the eight unscoped `binzo-*` names. For prereleases, add `--tag next` to both publish commands.
 
 To change a published binary, increment the version and rebuild; npm versions are immutable. If a publish is interrupted, publish the remaining workspaces individually with `npm publish --workspace <package-name>`.
 
@@ -203,4 +213,8 @@ npm pack --dry-run
 npm pack --workspace binzo-darwin-arm64 --dry-run
 ```
 
-`bun run build:npm` builds all platforms without publishing. npm installation requires optional dependencies and install scripts to be enabled. The install script only places the downloaded binary; it does not compile code or download additional files. If scripts were disabled, enable them and run `npm rebuild binzo` (`npm rebuild --global binzo` for a global installation).
+`bun run build:npm` builds all platforms without publishing. npm installation requires optional dependencies and install scripts to be enabled. The install script only places the downloaded binary; it does not compile code or download additional files. If scripts were disabled, enable them and run `npm rebuild binzo-cli` (`npm rebuild --global binzo-cli` for a global installation).
+
+## License
+
+[MIT](LICENSE).

package/install.cjs

@@ -31,7 +31,7 @@ function resolveBinary() {
     );
   }
 
-  const { version } = require("./package.json");
+  const { name: packageName, version } = require("./package.json");
   const name = `binzo-${platform}`;
   const executable = process.platform === "win32" ? "binzo.exe" : "binzo";
 
@@ -44,7 +44,7 @@ function resolveBinary() {
     return require.resolve(`${name}/bin/${executable}`);
   } catch (cause) {
     throw new Error(
-      `The Binzo binary package ${name}@${version} is missing or does not match this installation.\nReinstall with optional dependencies enabled:\n\n  npm install --global binzo@${version} --include=optional\n\nFor a local project, omit --global. Avoid copying node_modules between different operating systems or CPU architectures.`,
+      `The Binzo binary package ${name}@${version} is missing or does not match this installation.\nReinstall with optional dependencies enabled:\n\n  npm install --global ${packageName}@${version} --include=optional\n\nFor a local project, omit --global. Avoid copying node_modules between different operating systems or CPU architectures.`,
       { cause },
     );
   }

package/package.json

@@ -1,7 +1,8 @@
 {
   "name": "binzo-cli",
-  "version": "0.0.1",
+  "version": "0.0.3",
   "description": "Your tools, straight from the source.",
+  "license": "MIT",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/darylcecile/binzo.git"
@@ -45,14 +46,14 @@
     "yauzl": "^3.4.0"
   },
   "optionalDependencies": {
-    "binzo-darwin-arm64": "0.0.1",
-    "binzo-darwin-x64": "0.0.1",
-    "binzo-linux-arm64-gnu": "0.0.1",
-    "binzo-linux-arm64-musl": "0.0.1",
-    "binzo-linux-x64-gnu": "0.0.1",
-    "binzo-linux-x64-musl": "0.0.1",
-    "binzo-windows-arm64": "0.0.1",
-    "binzo-windows-x64": "0.0.1"
+    "binzo-darwin-arm64": "0.0.3",
+    "binzo-darwin-x64": "0.0.3",
+    "binzo-linux-arm64-gnu": "0.0.3",
+    "binzo-linux-arm64-musl": "0.0.3",
+    "binzo-linux-x64-gnu": "0.0.3",
+    "binzo-linux-x64-musl": "0.0.3",
+    "binzo-windows-arm64": "0.0.3",
+    "binzo-windows-x64": "0.0.3"
   },
   "engines": {
     "node": ">=20"