@hecks/client 3.0.4 → 3.1.0

package/README.md

@@ -276,7 +276,7 @@ The hermetic tests run a protocol scenario against an in-process fake of the
 host. `npm run test:contract` runs the same scenario against a live host; see
 `test/contract.mjs`. The repository's `client-contract` workflow starts
 `rust/host` on the `spec/fixtures/rust_host/checkout_fixture` domain and runs
-it. To do the same locally, build that domain with `hecks build_wasm`, start
+it. To do the same locally, build that domain with `hecks build.build_wasm`, start
 `rust/host`'s `bootstrap` binary with `HECKS_SERVE_MODE=1`, `HECKS_DOMAIN`,
 `HECKS_WASM_PATH`, `HECKS_IR_PATH` and `DATABASE_URL` (a Postgres database), and
 run `HECKS_SERVICE_URL=http://127.0.0.1:<port> npm run test:contract`. Add
@@ -288,7 +288,7 @@ routes (it started with `HECKS_CHECKOUT_DOMAIN` naming its domain) to check the
 
 The package version equals `Hecks::VERSION` and is released together with the
 gem; `spec/hecks_client_version_spec.rb` fails when they differ, and
-`hecks publish` (and `hecks publish_gem` on its own) refuses to publish while they do. When
+`hecks publishing_run.publish` (and `hecks publishing_run.publish_gem` on its own) refuses to publish while they do. When
 `lib/hecks/version.rb` changes, bump the package in the same change:
 
 ```sh
@@ -299,8 +299,8 @@ npm version <version> --no-git-tag-version   # also updates package-lock.json
 Pushing the release tag starts `.github/workflows/publish-client.yml`, which
 publishes the package with npm trusted publishing: a short-lived identity
 token from the workflow run, so no npm token and no one-time code is stored
-anywhere. `hecks publish` pushes the tag, publishes the gem, and waits for the
-package to appear on npm (`hecks publish --npm-only` waits again after a
+anywhere. `hecks publishing_run.publish` pushes the tag, publishes the gem, and waits for the
+package to appear on npm (`hecks publishing_run.publish --npm-only` waits again after a
 re-run; a version npm already has is skipped).
 
 One-time setup, by an owner of the `@hecks` scope, once the package exists:
@@ -309,10 +309,10 @@ Actions > organization or user `heckslabs`, repository `hecks`, workflow
 filename `publish-client.yml`, environment blank.
 
 The first publish, before that can be configured, and any emergency when CI is
-down, is `hecks publish --npm-local`. It publishes from this machine with a
+down, is `hecks publishing_run.publish --npm-local`. It publishes from this machine with a
 token held in 1Password: the "publish token" field on the "npmjs.com" item in
 the Hecks vault (`release/npm_publish.env` names the vault, item and field;
-the setup is in the header of `hecks publish`). That token must be a granular
+the setup is in the header of `hecks publishing_run.publish`). That token must be a granular
 token scoped Read and write to the `@hecks` scope with "Bypass two-factor
 authentication" enabled, and short-lived: the account's second factor is a
 passkey, so a token that requires a one-time code cannot publish (npm answers

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hecks/client",
-  "version": "3.0.4",
+  "version": "3.1.0",
   "description": "Client for the body-shaped dispatch protocol a Hecks host answers: read the domain, dispatch commands, read the answers.",
   "license": "Apache-2.0",
   "private": false,