@telorun/analyzer 0.62.0 → 0.62.1

package/dist/release/payload-digest.d.ts

@@ -25,9 +25,13 @@ export declare const MANIFEST_LAYER = "manifest";
  * Exactly one today, and for a structural reason rather than an omission: the
  * published `layers:` index lives *inside* `telo.yaml`, so it cannot carry that
  * file's own digest — the entry would have to be computed over bytes containing
- * it. Nor can the digest be recovered by hashing what the registry serves, since
- * the transport injects the index at push time and the published text is
- * therefore not the text the payload builder produced.
+ * it. `readPublishedDigests` reads that index, so it has no answer for this key.
+ *
+ * It is no longer *unknowable*, though, only absent from the index: the payload
+ * builder now writes the index, so its manifest is the published text and this
+ * digest is what hashing the served `telo.yaml` yields. Reconciling it would
+ * mean fetching the manifest per module rather than reading one index — worth
+ * doing, and a separate change from the one that made it possible.
  *
  * It stays in the ledger regardless, because it is the only thing that sees a
  * **manifest-only change**: a schema edit, a new kind, a description, a

package/dist/release/payload-digest.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"payload-digest.d.ts","sourceRoot":"","sources":["../../src/release/payload-digest.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;GAcG;AAEH,OAAO,EAAiB,KAAK,gBAAgB,EAAE,KAAK,SAAS,EAAE,MAAM,yBAAyB,CAAC;AAE/F,sDAAsD;AACtD,MAAM,MAAM,YAAY,GAAG,QAAQ,CAAC,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC,CAAC;AAE5D,yDAAyD;AACzD,eAAO,MAAM,cAAc,aAAa,CAAC;AAEzC;;;;;;;;;;;;;;;;GAgBG;AACH,eAAO,MAAM,sBAAsB,EAAE,WAAW,CAAC,MAAM,CAA6B,CAAC;AAErF;;;;;;;;;;GAUG;AACH,wBAAgB,cAAc,CAAC,IAAI,EAAE,SAAS,GAAG,MAAM,EAAE,QAAQ,CAAC,EAAE,gBAAgB,GAAG,MAAM,CAM5F;AAED;;;mBAGmB;AACnB,MAAM,WAAW,WAAW;IAC1B,QAAQ,CAAC,KAAK,EAAE,MAAM,CAAC;IACvB,QAAQ,CAAC,MAAM,CAAC,EAAE,MAAM,CAAC;IACzB,QAAQ,CAAC,KAAK,CAAC,EAAE,MAAM,CAAC;CACzB;AAED;mCACmC;AACnC,wBAAgB,gBAAgB,CAAC,MAAM,EAAE,YAAY,EAAE,KAAK,EAAE,YAAY,GAAG,WAAW,EAAE,CAQzF"}
+{"version":3,"file":"payload-digest.d.ts","sourceRoot":"","sources":["../../src/release/payload-digest.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;GAcG;AAEH,OAAO,EAAiB,KAAK,gBAAgB,EAAE,KAAK,SAAS,EAAE,MAAM,yBAAyB,CAAC;AAE/F,sDAAsD;AACtD,MAAM,MAAM,YAAY,GAAG,QAAQ,CAAC,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC,CAAC;AAE5D,yDAAyD;AACzD,eAAO,MAAM,cAAc,aAAa,CAAC;AAEzC;;;;;;;;;;;;;;;;;;;;GAoBG;AACH,eAAO,MAAM,sBAAsB,EAAE,WAAW,CAAC,MAAM,CAA6B,CAAC;AAErF;;;;;;;;;;GAUG;AACH,wBAAgB,cAAc,CAAC,IAAI,EAAE,SAAS,GAAG,MAAM,EAAE,QAAQ,CAAC,EAAE,gBAAgB,GAAG,MAAM,CAM5F;AAED;;;mBAGmB;AACnB,MAAM,WAAW,WAAW;IAC1B,QAAQ,CAAC,KAAK,EAAE,MAAM,CAAC;IACvB,QAAQ,CAAC,MAAM,CAAC,EAAE,MAAM,CAAC;IACzB,QAAQ,CAAC,KAAK,CAAC,EAAE,MAAM,CAAC;CACzB;AAED;mCACmC;AACnC,wBAAgB,gBAAgB,CAAC,MAAM,EAAE,YAAY,EAAE,KAAK,EAAE,YAAY,GAAG,WAAW,EAAE,CAQzF"}

package/dist/release/payload-digest.js

@@ -23,9 +23,13 @@ export const MANIFEST_LAYER = "manifest";
  * Exactly one today, and for a structural reason rather than an omission: the
  * published `layers:` index lives *inside* `telo.yaml`, so it cannot carry that
  * file's own digest — the entry would have to be computed over bytes containing
- * it. Nor can the digest be recovered by hashing what the registry serves, since
- * the transport injects the index at push time and the published text is
- * therefore not the text the payload builder produced.
+ * it. `readPublishedDigests` reads that index, so it has no answer for this key.
+ *
+ * It is no longer *unknowable*, though, only absent from the index: the payload
+ * builder now writes the index, so its manifest is the published text and this
+ * digest is what hashing the served `telo.yaml` yields. Reconciling it would
+ * mean fetching the manifest per module rather than reading one index — worth
+ * doing, and a separate change from the one that made it possible.
  *
  * It stays in the ledger regardless, because it is the only thing that sees a
  * **manifest-only change**: a schema edit, a new kind, a description, a

package/dist/telo-version.d.ts

@@ -1,3 +1,3 @@
 /** The surface generation this analyzer implements. */
-export declare const TELO_SURFACE_VERSION = "0.77.0";
+export declare const TELO_SURFACE_VERSION = "0.78.0";
 //# sourceMappingURL=telo-version.d.ts.map

package/dist/telo-version.js

@@ -5,4 +5,4 @@
 // its release identity, this is the scale a module's `requires.telo` range is
 // written against, and every kernel in every language reports the same scale.
 /** The surface generation this analyzer implements. */
-export const TELO_SURFACE_VERSION = "0.77.0";
+export const TELO_SURFACE_VERSION = "0.78.0";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@telorun/analyzer",
-  "version": "0.62.0",
+  "version": "0.62.1",
   "description": "Telo Analyzer - Static manifest validator for Telo manifests.",
   "keywords": [
     "telo",

package/src/release/payload-digest.ts

@@ -29,9 +29,13 @@ export const MANIFEST_LAYER = "manifest";
  * Exactly one today, and for a structural reason rather than an omission: the
  * published `layers:` index lives *inside* `telo.yaml`, so it cannot carry that
  * file's own digest — the entry would have to be computed over bytes containing
- * it. Nor can the digest be recovered by hashing what the registry serves, since
- * the transport injects the index at push time and the published text is
- * therefore not the text the payload builder produced.
+ * it. `readPublishedDigests` reads that index, so it has no answer for this key.
+ *
+ * It is no longer *unknowable*, though, only absent from the index: the payload
+ * builder now writes the index, so its manifest is the published text and this
+ * digest is what hashing the served `telo.yaml` yields. Reconciling it would
+ * mean fetching the manifest per module rather than reading one index — worth
+ * doing, and a separate change from the one that made it possible.
  *
  * It stays in the ledger regardless, because it is the only thing that sees a
  * **manifest-only change**: a schema edit, a new kind, a description, a

package/src/telo-version.ts

@@ -6,4 +6,4 @@
 // written against, and every kernel in every language reports the same scale.
 
 /** The surface generation this analyzer implements. */
-export const TELO_SURFACE_VERSION = "0.77.0";
+export const TELO_SURFACE_VERSION = "0.78.0";