space-data-module-sdk 0.2.8 → 0.2.9

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -223,6 +223,10 @@ Concrete multiaddrs, peer IDs, and producer routing do not belong in the
223
223
  canonical manifest. They belong in deployment metadata attached to the final
224
224
  package or bundle.
225
225
 
226
+ Deployment plans should key resolved protocol installations by `protocolId`.
227
+ They may include `wireId` as optional legacy metadata when a concrete transport
228
+ still needs it.
229
+
226
230
  This repo exposes that deployment surface from
227
231
  `space-data-module-sdk/deployment`. Use it to:
228
232
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "space-data-module-sdk",
3
- "version": "0.2.8",
3
+ "version": "0.2.9",
4
4
  "description": "Module SDK for building, validating, signing, and deploying WebAssembly modules on the Space Data Network.",
5
5
  "type": "module",
6
6
  "types": "./src/index.d.ts",
@@ -14,7 +14,7 @@ export type ScheduleBindingKindName = "interval" | "cron" | "once";
14
14
 
15
15
  export interface ResolvedProtocolInstallation {
16
16
  protocolId: string;
17
- wireId: string;
17
+ wireId?: string | null;
18
18
  transportKind: ProtocolTransportKindName | string;
19
19
  role: ProtocolRoleName | string;
20
20
  peerId?: string | null;
@@ -414,7 +414,7 @@ function validateProtocolInstallation(
414
414
  `${location}.protocolId`,
415
415
  "Protocol installation protocolId",
416
416
  );
417
- validateStringField(
417
+ validateOptionalStringField(
418
418
  issues,
419
419
  installation.wireId,
420
420
  `${location}.wireId`,