fm-bench 0.5.2 → 0.5.3

package/README.md

@@ -1,5 +1,7 @@
 # fm-bench
 
+[![CI](https://github.com/devinoldenburg/fm-bench/actions/workflows/ci.yml/badge.svg)](https://github.com/devinoldenburg/fm-bench/actions/workflows/ci.yml)
+
 Benchmark Apple's `fm` command on macOS 27+.
 
 Measure latency, throughput, streaming smoothness, stability, and goodput across Apple Foundation Models — with repeatable prompt suites and JSON/CSV reports for automation.

package/docs/releasing.md

@@ -0,0 +1,35 @@
+# Releasing
+
+`fm-bench` uses semver tags (`v*.*.*`). Pushing a tag runs the **Release** workflow: test, lint, npm publish (with provenance), and GitHub release notes.
+
+## Prerequisites
+
+- Repository secret **`NPM_TOKEN`**: npm automation token with publish access to `fm-bench`.
+- **`main`** is green on CI.
+
+## Option A — GitHub Actions (recommended)
+
+1. Open **Actions → Version → Run workflow**.
+2. Choose `patch`, `minor`, `major`, or an exact semver.
+3. The job runs `npm version`, pushes the commit and tag to `main`.
+4. The tag push triggers **Release** automatically.
+
+## Option B — Local
+
+```sh
+npm ci && npm test && npm run lint
+npm version patch   # or minor / major
+git push --follow-tags
+```
+
+## Re-run Release without republishing
+
+If npm already has the version but GitHub release failed (or vice versa), use **Actions → Release → Run workflow** and enter the existing tag (for example `v0.5.3`). The workflow skips npm publish when that version is already on the registry and skips creating a duplicate GitHub release.
+
+## Dry run
+
+```sh
+npm run publish:dry-run
+```
+
+CI runs the same dry-run on every push to `main` and on pull requests.

package/package.json

@@ -1,10 +1,10 @@
 {
   "name": "fm-bench",
-  "version": "0.5.2",
+  "version": "0.5.3",
   "description": "Dynamic benchmark CLI for Apple's fm command on macOS 27+.",
   "type": "module",
   "bin": {
-    "fm-bench": "./bin/fm-bench.js"
+    "fm-bench": "bin/fm-bench.js"
   },
   "files": [
     "bin",