cf-nix-cache 0.1.0 → 0.1.2

package/README.md

@@ -1,15 +1,16 @@
 # `cf-nix-cache`
 
-This package contains the compiled Worker runtime used by the public
-`cf-nix-cache-template`. It is intentionally separate from the development
-monorepo: customers upgrade this package, while their Wrangler configuration,
-resource names, scaling, placement, routes, and observability settings remain
-owned by their deployment repository.
+This package is the cf-nix-cache Worker. Its source lives here; the published
+package contains only the compiled bundle used by the public
+`cf-nix-cache-template`. Customers upgrade this package, while their Wrangler
+configuration, resource names, scaling, placement, routes, and observability
+settings remain owned by their deployment repository.
 
 Every published version includes `release-manifest.json`. The manifest pins
 the matching processor to an immutable `linux/amd64` image digest so a package
 upgrade cannot accidentally deploy a different container.
 
 `releaseReady` is set to `false` by the Changesets version step and becomes
-`true` only in the reviewed digest-pinning PR. Publication workflows must
+`true` once the Release PR job has published the processor image and pinned
+its digest. Publication workflows must
 reject manifests that have not been finalized.

package/dist/index.d.ts

@@ -1,2 +1,14 @@
-export { default } from './index.js';
-export * from './index.js';
+declare const worker: {
+  fetch(request: Request, env: unknown, ctx: unknown): Promise<Response>;
+};
+export default worker;
+export declare class AuditLog {}
+export declare class CacheCoordinator {}
+export declare class CacheIndexShard {}
+export declare class ContainerProxy {}
+export declare class DeleteCacheWorkflow {}
+export declare class ProcessorContainer {}
+export declare class ProcessUploadWorkflow {}
+export declare class SystemControl {}
+export declare class TokenCatalog {}
+export declare class UploadJob {}