@heroiclands/package-build 3.1.0 → 3.2.0

package/CHANGELOG.md

@@ -1,5 +1,30 @@
 # @heroiclands/package-build
 
+## 3.2.0
+
+### Minor Changes
+
+- a5f07a3: Let a system-agnostic module stamp no system version.
+  
+  #40 made `stats.systemId` optional. `stats.systemVersion` stayed mandatory and
+  derived — from the `compatibility.verified` of a declared system relationship,
+  throwing when there is none — and a data configuration may not declare it
+  directly. A module that deliberately targets no system therefore could not be
+  configured at all.
+  
+  Declaring the relationship is not an escape. Foundry's `_testSupportedSystems`
+  returns true when a package declares no systems, but returns false when it
+  declares some and none of them is installed. Naming `hm3` and `sohl` would make
+  such a module unavailable to a world running anything else — the opposite of
+  what a system-agnostic package is for.
+  
+  `shippedSystemVersion` now returns `null` when a module names **neither** a
+  `stats.systemId` **nor** any `relationships.systems`, and `stats.systemVersion`
+  is optional alongside it. Every other case is unchanged: a module that names a
+  system but declares no usable relationship still throws, because that is the
+  mistake #1548 added the guard for. The two signals together are what separate
+  system-agnostic on purpose from a forgotten declaration.
+
 ## 3.1.0
 
 ### Minor Changes

package/content-config.mjs

@@ -816,10 +816,15 @@ function normalizeStats(value) {
             input.systemId === undefined || input.systemId === null ?
                 null
             :   requireNonEmptyString(input.systemId, "stats.systemId"),
-        systemVersion: requireNonEmptyString(
-            input.systemVersion,
-            "stats.systemVersion",
-        ),
+        // Optional for the same reason as `systemId`: a system-agnostic module
+        // is not built against a system, so it has no version of one to stamp.
+        systemVersion:
+            input.systemVersion === undefined || input.systemVersion === null ?
+                null
+            :   requireNonEmptyString(
+                    input.systemVersion,
+                    "stats.systemVersion",
+                ),
         lastModifiedBy: requireNonEmptyString(
             input.lastModifiedBy,
             "stats.lastModifiedBy",

package/engine/pack-config.mjs

@@ -272,6 +272,23 @@ function shippedSystemVersion(rootDir, input) {
 
     const systemId = /** @type {Record<string, unknown>} */ (input.stats ?? {})
         .systemId;
+    const declaredSystems = /** @type {Record<string, unknown>} */ (
+        input.relationships ?? {}
+    ).systems;
+
+    // A module that names neither a system nor a relationship with one is
+    // system-agnostic on purpose: its packs are core document types carrying no
+    // system data, and it installs under any system. There is no version to
+    // stamp, and inventing one would be the very thing the throw below guards
+    // against. The two signals together are what separate this from a module
+    // that simply forgot to declare its system (#43).
+    if (
+        (systemId === undefined || systemId === null) &&
+        !(Array.isArray(declaredSystems) && declaredSystems.length)
+    ) {
+        return null;
+    }
+
     const systems =
         /** @type {{id?: string, compatibility?: {verified?: string}}[]} */ (
             /** @type {Record<string, unknown>} */ (input.relationships ?? {})

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@heroiclands/package-build",
-    "version": "3.1.0",
+    "version": "3.2.0",
     "description": "Shared toolchain for building and shipping a HeroicLands Foundry VTT package — content compilation, manifest, localization, staging, bundle, release and deployment.",
     "license": "GPL-3.0-or-later",
     "type": "module",