@bygghammar/cms-platform 0.91.0 → 0.91.1

package/CHANGELOG.md

@@ -8,6 +8,42 @@ matches `package.json` exactly. See
 Versions 0.1.0 through 0.78.0 predate this repository and were reconstructed
 from the published npm tarballs.
 
+## 0.91.1
+
+- Documentation correction, and nothing else. The npm-facing `README.md` said
+  contract v2 arrives with "the two `20260904…` publication migrations". Those
+  two are what v2 needs in order to work, but they are not the upgrade: a site
+  coming directly from `0.90.0-m7.12` is missing all three new canonical
+  migrations and must apply them in chronological order —
+  `20260904090000_c54603f8-a155-40f8-a86c-54434aa5c0ae.sql`,
+  `20260904140000_9f2a7c41-06d5-4d6b-8b4e-1c7a5d3e9b20.sql`, then
+  `20260904160000_0d565000-2839-4738-aacc-537d7090398f.sql`.
+- The last two are the contract-v2 publication pair. Applying only that pair
+  leaves `missingMigrations` and `compareSchema` reporting
+  `20260904090000_c54603f8-…` as still missing, because it is canonical schema
+  too and not merely a prerequisite of the pair.
+- `assertPlatformContract(2)` compares contract numbers held in the site's own
+  code. It never inspects the database, so a site that passes it has proved
+  nothing about schema parity. The README now says so, and
+  `tests/platform-contract.test.ts` holds the README to it alongside
+  `docs/NEW-SITE.md` and `docs/PAGES.md`.
+- No runtime source, migration SQL, database schema or application behaviour
+  changes in this release. Compared with `0.91.0`, the published npm package
+  changes only `README.md`, `CHANGELOG.md` and `package.json`, and the README is
+  the one carrying the user-facing correction. The repository differs by more
+  than the package does: it also holds the README regression test in
+  `tests/platform-contract.test.ts` and the release-workflow hardening merged
+  after `0.91.0`, which taught release verification to wait out npm's
+  asynchronous publishing. Neither of those is included in the npm package.
+
+**Already running `0.91.0`?** The package was correct; only its README was
+incomplete, so there is nothing to roll back and no reason to republish. Check
+the database rather than the version: run `missingMigrations(applied)` or
+`compareSchema(applied)` against the migration list your site has actually
+applied, apply any canonical migration they report missing before letting
+editors make further changes, and do not treat contract version 2 as evidence
+of schema parity.
+
 ## 0.91.0
 
 - Stable promotion of `0.91.0-m7.1`. There are no runtime source, database

package/README.md

@@ -60,9 +60,22 @@ related is ever read in the browser, and the font picker needs no API key. See
 - `PLATFORM_CONTRACT_VERSION` (`platform/contract`) is bumped when a shared
   screen starts requiring schema or adapter capabilities an older site lacks.
   Sites pin it in a test. It is **v2**: page saves, publishing, trashing and
-  restoring go through database functions that the two `20260904…` publication
-  migrations install, so migrations are applied before the package is deployed.
-  `docs/NEW-SITE.md` gives the order.
+  restoring go through database functions. Upgrading straight from the last
+  pre-v2 published package, `0.90.0-m7.12`, means applying all three new
+  canonical migrations, in chronological order:
+
+  1. `20260904090000_c54603f8-a155-40f8-a86c-54434aa5c0ae.sql`
+  2. `20260904140000_9f2a7c41-06d5-4d6b-8b4e-1c7a5d3e9b20.sql`
+  3. `20260904160000_0d565000-2839-4738-aacc-537d7090398f.sql`
+
+  The last two are the pair that establishes contract-v2 publication
+  behaviour, but the first is canonical schema too, so applying only the pair
+  still leaves `missingMigrations` and `compareSchema` reporting drift. Apply
+  them before the v2 package is deployed, then verify the two things
+  separately: `missingMigrations(applied)` reports nothing missing, **and**
+  `assertPlatformContract(2)` passes. The second only compares version numbers
+  in the site's own code and never reads the database, so it is no substitute
+  for the first. `docs/NEW-SITE.md` gives the full order.
 - `migrations/` is schema only. Site content, SEO copy and seeds never belong
   there.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bygghammar/cms-platform",
-  "version": "0.91.0",
+  "version": "0.91.1",
   "description": "Shared CMS platform: blocks, block types, i18n core, UI primitives and design-token contract used by every Bygghammar/Voyara site.",
   "type": "module",
   "sideEffects": [