@marvalt/digivalt-core 0.2.34 → 0.2.35

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/CHANGELOG.md CHANGED
@@ -5,6 +5,13 @@ All notable changes to this project will be documented in this file.
5
5
  The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
6
6
  and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
7
7
 
8
+ ## [0.2.35] - 2026-09-23
9
+
10
+ ### Fixed
11
+ - WordPress generation rejects a payload that does not contain the configured front page, restores the previous `wordpress-data.json`, and returns failure so the build exits. A two-page multi-frontend payload that includes the front page still passes. Fixture mode (`VITE_IS_LOVABLE`) skips the check.
12
+
13
+ **Publish/deploy:** publish **`@marvalt/digivalt-core@0.2.35`**. Then bump consumer apps (including **digivalt-landing**, whose lockfile still pins 0.2.32) and redeploy. No WordPress plugin publish.
14
+
8
15
  ## [0.2.34] - 2026-09-22
9
16
 
10
17
  ### Added
@@ -0,0 +1,11 @@
1
+ export type WordPressPayloadCheck = {
2
+ ok: true;
3
+ warnEmptyChrome: boolean;
4
+ } | {
5
+ ok: false;
6
+ expectedSlug?: string;
7
+ pageCount: number;
8
+ receivedSlugs: string[];
9
+ };
10
+ /** Reject a WordPress payload that cannot be the app's front page. */
11
+ export declare function checkWordPressPayload(payload: unknown): WordPressPayloadCheck;