@sequenceholdings/artifact-studio 0.6.2 → 0.6.4

package/dist/manifest-next-ingress.js

@@ -160,9 +160,9 @@ export function validateIngressAgainstServer({ server, ctx }) {
             ctx.addIssue({ code: 'custom', path: [...at, 'service_account'], message: 'Each ingress needs its own service account' });
         }
         serviceAccounts.add(ingress.service_account);
-        // TODO(C5/P4): these are reference strings, so a UUID here and a slug on the server for the same
-        // account pass. The binding/attachment step must resolve both to account ids and refuse an
-        // ingress account equal to the app's account (C5 acceptance item).
+        // These are reference strings, so a UUID here and a slug on the server for the same account pass.
+        // Atlas's deploy preflight resolves both to account ids and refuses an ingress account equal to
+        // the app's or to another ingress's (preflightArtifactAttachments).
         if (server.service_account !== undefined && ingress.service_account === server.service_account) {
             ctx.addIssue({ code: 'custom', path: [...at, 'service_account'], message: 'An ingress service account must differ from server.service_account' });
         }

package/dist/server/internal/verify-any.d.ts

@@ -3,7 +3,9 @@ export type AnyArtifactRequestContext = ArtifactRequestContext | RequestContextV
 /**
  * Version-dispatching verifier for platform code that must accept both Atlas-user (v1) and
  * external (v2) contexts, such as the broker. Applications never get this: it is not exported
- * from `./server` or `./server/context`, and the exports map does not expose `server/internal`.
+ * from `./server` or `./server/context`, and the exports map names no `./server/internal` subpath,
+ * so a package import of it fails to resolve. Atlas, the only consumer, reaches the built file
+ * through its own resolver aliases (tsconfig `paths`, Next and Vitest `resolve.alias`).
  *
  * Kid and version are paired both ways: an `external-` kid must sign a v2 context, and a v2
  * context must be signed by an `external-` kid. This pairing is the only thing standing between

package/dist/server/internal/verify-any.js

@@ -5,7 +5,9 @@ import { canonicalizeIngressPath, signedIngressPath } from '../ingress-routes.js
 /**
  * Version-dispatching verifier for platform code that must accept both Atlas-user (v1) and
  * external (v2) contexts, such as the broker. Applications never get this: it is not exported
- * from `./server` or `./server/context`, and the exports map does not expose `server/internal`.
+ * from `./server` or `./server/context`, and the exports map names no `./server/internal` subpath,
+ * so a package import of it fails to resolve. Atlas, the only consumer, reaches the built file
+ * through its own resolver aliases (tsconfig `paths`, Next and Vitest `resolve.alias`).
  *
  * Kid and version are paired both ways: an `external-` kid must sign a v2 context, and a v2
  * context must be signed by an `external-` kid. This pairing is the only thing standing between

package/package.json

@@ -9,7 +9,7 @@
   "publishConfig": {
     "access": "public"
   },
-  "version": "0.6.2",
+  "version": "0.6.4",
   "description": "SDK types and CLI library for building Artifact Studio apps. Driven via `seq-studio artifact <sub>` (@sequenceholdings/studio-cli), which runs the `./cli` runCli export.",
   "type": "module",
   "exports": {
@@ -168,7 +168,7 @@
     "parse5": "7.3.0",
     "@sequenceholdings/lattice-form-renderer": "0.2.0",
     "@sequenceholdings/storage": "0.1.0",
-    "@sequenceholdings/orm": "2.3.0"
+    "@sequenceholdings/orm": "2.4.0"
   },
   "devDependencies": {
     "@types/js-yaml": "^4.0.9",