@kanonak-protocol/cli 8.5.1 → 8.7.0

package/dist/commands/hash.d.ts

@@ -21,6 +21,10 @@
  * Prints the hash on stdout and `--verbose` also prints the
  * canonical form (the JSON that was hashed) on stderr so a user
  * debugging a hash divergence can compare forms.
+ *
+ * Every import is read at the version it states, never at a lock's pin
+ * or the newest release (kanonak-protocol 4.8.0, `stated-version-rule`),
+ * so one version hashes one way wherever and whenever it's hashed.
  */
 export declare function hashCommand(target: string, options?: {
     verbose?: boolean;

package/dist/commands/releaseLock.d.ts

@@ -0,0 +1,21 @@
+/**
+ * `kanonak release-lock` — record the release lock of every published version in this folder that has none
+ * (kanonak-protocol 4.9.0, `release-lock-rule`): the version and the closure it resolves to now, written beside its
+ * source as `{name}.kanonak.lock`, for `kanonak publish` and `kanonak serve` to serve at the discovery document's
+ * `release_lock_url_template`.
+ *
+ * A published version is a source named for its version, `{version}.kan.yml` or `{package}@{version}.kan.yml`,
+ * whose bytes never change, as `kanonak upgrade` reads it. A release lock is recorded once and never changes, so one
+ * already recorded is left as it is: run this when a version is published, and commit what it writes. With `check`,
+ * nothing is written, and it exits 1 when a version has none.
+ *
+ * With `files`, only those versions are recorded, each of which must be a published version. A version published
+ * before release locks were recorded gets its own by running this at the commit that published it, naming the
+ * versions that commit added, so it resolves against the versions held then. Run that with `offline`, and an empty
+ * package cache: a dependency the folder didn't hold then is refused, naming it, rather than resolved to the newest
+ * version a registry serves today, which that version's closure never held.
+ */
+export declare function releaseLockCommand(options: {
+    check?: boolean;
+    offline?: boolean;
+}, files?: string[]): Promise<void>;

package/dist/commands/upgrade.d.ts

@@ -11,7 +11,12 @@
  * change, so the new version is written beside it under its own name. Any
  * other source is the package's one file, and is edited in place. With
  * `check`, nothing is written, and it exits 1 when anything would change.
+ *
+ * `sourceOf` names the publishers whose source this folder is: their versions
+ * are the ones it holds, and their lock is never fetched, as a folder holding
+ * a gated publisher's sources needs.
  */
 export declare function upgradeCommand(options: {
     check?: boolean;
+    sourceOf?: string[];
 }): Promise<void>;