@peakflo/agent-harness 0.2.1-rc.3 → 0.2.2

package/README.md

@@ -36,4 +36,34 @@ Optional flags include `--health-port <port>`, `--runtime <desktop|self-hosted>`
 `--workspace-root <path>`, and `--github-proxy-port <port>`. Run
 `npx @peakflo/agent-harness@rc --help` for the full list.
 
+## Releasing
+
+`.github/scripts/agent-harness-release.mjs` publishes this package
+automatically: an rc from `main` on every push, a final from `production`.
+**`version` in this package's `package.json` is a FLOOR, not the release** —
+the lowest version the pipeline may produce, not the version it will produce.
+The pipeline reads the registry and computes the actual version on every run:
+
+1. `latestFinal` = the highest already-published **final** (non-prerelease)
+   version that is `>= floor`.
+2. If this tree's content is byte-identical to `latestFinal`'s (ignoring only
+   the `version` field), there is nothing to publish on **either** channel —
+   `latestFinal` is reused as the version to pin. This is the common case:
+   most deploys do not touch the harness at all.
+3. Otherwise `next = max(floor, patch(latestFinal) + 1)` — or just `floor`
+   when there is no `latestFinal` at or above it (a floor a human just
+   raised). The rc channel publishes `${next}-rc.N` (reusing an identical
+   existing rc rather than republishing); the final channel publishes `next`,
+   after confirming an rc of `next` has this exact content.
+
+**A routine patch release needs no PR at all** — pushing a harness change to
+`main` and then to `production` is enough; the version above `floor` is
+computed, not hand-written. **A minor or major bump is still a human
+decision**: raise `version` in `packages/agent-harness/package.json` (e.g.
+`0.2.1` -> `0.3.0`) and the next computed release starts from there.
+
+See the comments above `contentDigest()`, `planRelease()` and `release()` in
+`agent-harness-release.mjs` for the full reasoning, including how two
+concurrent runs are kept from publishing the same version.
+
 Licensed under the MIT License. See [LICENSE](./LICENSE).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@peakflo/agent-harness",
-  "version": "0.2.1-rc.3",
+  "version": "0.2.2",
   "description": "Headless Peakflo coding-agent harness. One codebase, three hosting modes: a Daytona cloud sandbox, a customer VM, and the 20x desktop.",
   "license": "MIT",
   "type": "commonjs",