lanekeep 0.3.1 → 0.4.0

package/README.md

@@ -97,23 +97,37 @@ A warm run with no changes executes no JavaScript at all — every file is a cac
 
 ## Installation
 
-Not yet published. The distribution is built and tested — one npm package per platform plus a
-launcher that resolves the right one, and every crate publishable to crates.io — but no
-version has been released yet.
+Pick whichever matches the project you are adding it to:
 
-When it ships:
+```bash
+npm install --save-dev lanekeep      # Node
+pip install lanekeep                 # Python
+brew install fmsouza/tap/lanekeep    # macOS and Linux, system-wide
+cargo install lanekeep-cli           # from source
+```
+
+For a Go project, pin it in `go.mod` alongside your other tools:
 
 ```bash
-npm install --save-dev lanekeep    # or: cargo install lanekeep-cli
+go get -tool github.com/fmsouza/lanekeep/cmd/lanekeep
 ```
 
-A single static binary with the JavaScript engine compiled in. **Node.js is not required to
-run lanekeep**, even though rules are written in TypeScript — it is required only to install
-it from npm, where it picks which binary to fetch.
+then `go tool lanekeep check ./...`. Go can only install and pin things written in Go, so
+that package is a small launcher which fetches the real binary on first use, verifies it
+against the release's published checksums, and caches it. Set `LANEKEEP_BINARY` to an
+already-installed lanekeep and it fetches nothing.
+
+Or download a binary from the [releases page](https://github.com/fmsouza/lanekeep/releases).
+
+A single static binary with the JavaScript engine compiled in. **No runtime is required to run
+lanekeep**, even though rules are written in TypeScript — Node, Python or Go is needed only to
+install it from that ecosystem, where it picks which binary to fetch. Nothing is pulled in as a
+dependency any of those ways.
 
-Prebuilt for macOS on Apple silicon, Linux on x86-64 and arm64, and Windows on x86-64.
-Intel macOS is not prebuilt — `cargo install lanekeep-cli` builds it from source, and the
-npm launcher says so rather than failing obscurely.
+Prebuilt for macOS on Apple silicon, Linux on x86-64 and arm64, and Windows on x86-64. The
+Linux binaries are built against glibc 2.17, so they run on anything from RHEL 7 onwards.
+Intel macOS is not prebuilt — `cargo install lanekeep-cli` builds it from source, and both the
+npm launcher and the Homebrew formula say so rather than failing obscurely.
 
 See [`docs/releasing.md`](docs/releasing.md) for how a release is cut.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "lanekeep",
-  "version": "0.3.1",
+  "version": "0.4.0",
   "description": "Deterministic, AST-based architectural conformance checking",
   "license": "MIT OR Apache-2.0",
   "repository": {
@@ -20,9 +20,9 @@
     "node": ">=18"
   },
   "optionalDependencies": {
-    "@lanekeep/darwin-arm64": "0.3.1",
-    "@lanekeep/linux-arm64": "0.3.1",
-    "@lanekeep/linux-x64": "0.3.1",
-    "@lanekeep/win32-x64": "0.3.1"
+    "@lanekeep/darwin-arm64": "0.4.0",
+    "@lanekeep/linux-arm64": "0.4.0",
+    "@lanekeep/linux-x64": "0.4.0",
+    "@lanekeep/win32-x64": "0.4.0"
   }
 }