@lunora/bindings 1.0.0-alpha.94 → 1.0.0-alpha.96

package/dist/ai-search/index.d.mts

@@ -6,7 +6,7 @@
  * aliased from `@cloudflare/workers-types`: `AiSearchNamespace` only ships in
  * workers-types 4.20260331.1+, and an alias resolved against an older (or
  * absent) install would silently degrade to `any` under `skipLibCheck`. The
- * mirror follows workers-types 5.20260929.1; a type test pins that the real
+ * mirror follows workers-types 5.20261002.1; a type test pins that the real
  * binding still satisfies it, so drift fails CI instead of the consumer.
  */
 /** A single message in a conversation-style search or chat request. */

package/dist/ai-search/index.d.ts

@@ -6,7 +6,7 @@
  * aliased from `@cloudflare/workers-types`: `AiSearchNamespace` only ships in
  * workers-types 4.20260331.1+, and an alias resolved against an older (or
  * absent) install would silently degrade to `any` under `skipLibCheck`. The
- * mirror follows workers-types 5.20260929.1; a type test pins that the real
+ * mirror follows workers-types 5.20261002.1; a type test pins that the real
  * binding still satisfies it, so drift fails CI instead of the consumer.
  */
 /** A single message in a conversation-style search or chat request. */

package/dist/artifacts/index.d.mts

@@ -5,17 +5,19 @@
  * and READS commits, trees, blobs and files. It has no write method: every write
  * is a `git push` over HTTPS with one of those tokens.
  *
- * Declared structurally (the `ImagesBindingLike` pattern) rather than leaning on
- * the global `Artifacts` type, because the pinned `@cloudflare/workers-types`
- * lags the runtime: it lacks `info()`, `log()`, `readCommit()`, `readTree()`,
- * `readBlob()` and `readFile()`, and it models `ArtifactsRepo` as carrying its
- * metadata as properties, which the deployed binding does not do (call
- * `info()`). The shapes here follow the Workers-binding docs and
- * `@cloudflare/workers-types@5.20261002.1`, the first release that matches them.
+ * Declared structurally (the `ImagesBindingLike` pattern) rather than aliasing
+ * the global `Artifacts` type, because an alias resolves against whatever
+ * `@cloudflare/workers-types` the app installed, and two lines get it wrong.
+ * The v4 line has no `Artifacts` global at all, so the alias is a silent `any`
+ * under `skipLibCheck`. v5 releases before 5.20261002.1 have a WRONG shape: no
+ * `info()`, `log()` or `read*()` methods, and `ArtifactsRepo` typed as carrying
+ * its metadata as properties, which the deployed binding does not do (call
+ * `info()`), so the alias is a wrong type.
  *
- * TODO(workers-types): once the catalog pin includes the read methods, add a
- * type test asserting the global `Artifacts` is assignable to
- * {@link ArtifactsBindingLike}.
+ * The shapes here follow the Workers-binding docs and
+ * `@cloudflare/workers-types@5.20261002.1`; `__tests__/artifacts/types.test.ts`
+ * pins that the global `Artifacts` / `ArtifactsRepo` still satisfy them, so
+ * drift fails CI.
  */
 /** A repo-scoped Git token's scope: `read` covers clone/fetch/pull, `write` adds push. */
 type ArtifactsTokenScope = "read" | "write";

package/dist/artifacts/index.d.ts

@@ -5,17 +5,19 @@
  * and READS commits, trees, blobs and files. It has no write method: every write
  * is a `git push` over HTTPS with one of those tokens.
  *
- * Declared structurally (the `ImagesBindingLike` pattern) rather than leaning on
- * the global `Artifacts` type, because the pinned `@cloudflare/workers-types`
- * lags the runtime: it lacks `info()`, `log()`, `readCommit()`, `readTree()`,
- * `readBlob()` and `readFile()`, and it models `ArtifactsRepo` as carrying its
- * metadata as properties, which the deployed binding does not do (call
- * `info()`). The shapes here follow the Workers-binding docs and
- * `@cloudflare/workers-types@5.20261002.1`, the first release that matches them.
+ * Declared structurally (the `ImagesBindingLike` pattern) rather than aliasing
+ * the global `Artifacts` type, because an alias resolves against whatever
+ * `@cloudflare/workers-types` the app installed, and two lines get it wrong.
+ * The v4 line has no `Artifacts` global at all, so the alias is a silent `any`
+ * under `skipLibCheck`. v5 releases before 5.20261002.1 have a WRONG shape: no
+ * `info()`, `log()` or `read*()` methods, and `ArtifactsRepo` typed as carrying
+ * its metadata as properties, which the deployed binding does not do (call
+ * `info()`), so the alias is a wrong type.
  *
- * TODO(workers-types): once the catalog pin includes the read methods, add a
- * type test asserting the global `Artifacts` is assignable to
- * {@link ArtifactsBindingLike}.
+ * The shapes here follow the Workers-binding docs and
+ * `@cloudflare/workers-types@5.20261002.1`; `__tests__/artifacts/types.test.ts`
+ * pins that the global `Artifacts` / `ArtifactsRepo` still satisfy them, so
+ * drift fails CI.
  */
 /** A repo-scoped Git token's scope: `read` covers clone/fetch/pull, `write` adds push. */
 type ArtifactsTokenScope = "read" | "write";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lunora/bindings",
-  "version": "1.0.0-alpha.94",
+  "version": "1.0.0-alpha.96",
   "description": "Lightweight Cloudflare binding helpers for Lunora — ctx.kv, ctx.images, ctx.analytics, ctx.pipelines, ctx.vectors, ctx.r2sql, ctx.artifacts, ctx.aiSearch, ctx.analyticsSql — one install, per-binding subpaths",
   "keywords": [
     "ai-search",
@@ -80,7 +80,7 @@
   },
   "dependencies": {
     "@lunora/errors": "1.0.0-alpha.50",
-    "@lunora/platform": "1.0.0-alpha.53"
+    "@lunora/platform": "1.0.0-alpha.55"
   },
   "engines": {
     "node": "^22.15.0 || >=24.11.0"