@decocms/blocks 7.52.0 → 7.53.0

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.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/src/cms/schema.ts +3 -3
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@decocms/blocks",
3
- "version": "7.52.0",
3
+ "version": "7.53.0",
4
4
  "type": "module",
5
5
  "engines": {
6
6
  "node": ">=24"
package/src/cms/schema.ts CHANGED
@@ -1104,9 +1104,9 @@ export function composeMeta(siteMeta: MetaResponse, options?: ComposeMetaOptions
1104
1104
  // Idempotency guard. composeMeta is NOT structurally idempotent — it appends
1105
1105
  // the framework section refs to `root.sections.anyOf` (and `__SECTION_REF__`),
1106
1106
  // so composing an already-composed meta a second time duplicates those refs.
1107
- // Since self-contained meta.gen.json is now baked at generation time (via the
1108
- // CLI's --compose), the tanstack runtime re-runs composeMeta on the file it
1109
- // loads from disk. A composed meta always carries a top-level `framework`
1107
+ // Since self-contained meta.gen.json is now baked at generation time (the CLI
1108
+ // always composes before writing), the tanstack runtime re-runs composeMeta
1109
+ // on the file it loads from disk. A composed meta always carries a `framework`
1110
1110
  // field, which raw generateMeta() output never sets — use it as the sentinel
1111
1111
  // and return the already-composed meta unchanged. Raw metas (framework unset,
1112
1112
  // e.g. sites generated by an older CLI) still compose normally, so this stays