@heroiclands/package-build 3.0.0 → 3.0.1

package/CHANGELOG.md

@@ -1,5 +1,15 @@
 # @heroiclands/package-build
 
+## 3.0.1
+
+### Patch Changes
+
+- 73a7e60: Correct the release the merge is dated to: 3.0.0, not 2.0.0.
+  
+  The merge commit set `version` by hand _and_ carried a major changeset, so
+  changesets bumped it a second time. `MIGRATING.md` was the live defect — it told
+  a consumer to install `^2.0.0`, which resolves nowhere.
+
 ## 3.0.0
 
 ### Major Changes

package/MIGRATING.md

@@ -1,7 +1,7 @@
-# Migrating to `@heroiclands/package-build` 2.0.0
+# Migrating to `@heroiclands/package-build` 3.0.0
 
 `@heroiclands/content-build` and `@heroiclands/package-build` are one package.
-The content half now ships inside `@heroiclands/package-build` at 2.0.0;
+The content half now ships inside `@heroiclands/package-build` at 3.0.0;
 `@heroiclands/content-build` is deprecated and receives no further releases.
 
 Nothing about how a build _works_ changed. This is a packaging change: the same
@@ -22,13 +22,13 @@ that touched a single idea.
 
 ## 1. Dependencies
 
-Drop `@heroiclands/content-build` and move to 2.0.0:
+Drop `@heroiclands/content-build` and move to 3.0.0:
 
 ```diff
  "devDependencies": {
 -  "@heroiclands/content-build": "^1.8.2",
 -  "@heroiclands/package-build": "^0.6.1"
-+  "@heroiclands/package-build": "^2.0.0"
++  "@heroiclands/package-build": "^3.0.0"
  }
 ```
 

package/README.md

@@ -14,7 +14,7 @@ The content half is documented separately in **[CONTENT.md](CONTENT.md)** — th
 note format, the pack pipeline, and the configuration contract a content tree
 declares itself with.
 
-> **This package was two.** Until 2.0.0 the content half shipped as
+> **This package was two.** Until 3.0.0 the content half shipped as
 > `@heroiclands/content-build`. No consumer ever installed one without the
 > other, and the packaging half depended on the content half besides, so the
 > boundary bought nothing and cost a configuration file with two owners and a

package/config.mjs

@@ -29,7 +29,7 @@
  * loader checks that the section is a mapping and hands it back frozen;
  * everything inside it is validated here.
  *
- * **That section used to be a reservation.** Until 2.0.0 these were two
+ * **That section used to be a reservation.** Until 3.0.0 these were two
  * packages, and `packageBuild:` was a block `@heroiclands/content-build`
  * carried on behalf of a toolchain it knew nothing about. One package now owns
  * the whole file, so it is an ordinary section — but the validation split is

package/engine/pack-config.mjs

@@ -94,7 +94,7 @@ export const CONFIG_BASENAME = "package-build.config";
  * reach for them: YAML first, `.mjs` last.
  *
  * The `content-build.config.*` stem this package read before the two toolchains
- * merged is **not** resolved. 2.0.0 renames the file rather than accepting both:
+ * merged is **not** resolved. 3.0.0 renames the file rather than accepting both:
  * a deprecation window here would mean a repository could sit indefinitely on a
  * name for a package that no longer exists, and the upgrade already requires
  * touching the consumer's manifest and imports.

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@heroiclands/package-build",
-    "version": "3.0.0",
+    "version": "3.0.1",
     "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",

package/types/engine/pack-config.d.mts

@@ -67,7 +67,7 @@ export const CONFIG_BASENAME: "package-build.config";
  * reach for them: YAML first, `.mjs` last.
  *
  * The `content-build.config.*` stem this package read before the two toolchains
- * merged is **not** resolved. 2.0.0 renames the file rather than accepting both:
+ * merged is **not** resolved. 3.0.0 renames the file rather than accepting both:
  * a deprecation window here would mean a repository could sit indefinitely on a
  * name for a package that no longer exists, and the upgrade already requires
  * touching the consumer's manifest and imports.