@decocms/parity 0.24.0 → 0.25.1
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 +32 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -5,6 +5,38 @@ 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.1.0/),
|
|
6
6
|
and this project adheres to [Semantic Versioning](https://semver.org/).
|
|
7
7
|
|
|
8
|
+
## [0.25.1] — 2026-08-20
|
|
9
|
+
|
|
10
|
+
### Fixed
|
|
11
|
+
|
|
12
|
+
* **FastStore v4 target skill: Content Platform, not legacy Headless CMS.** The
|
|
13
|
+
`target-faststore-v4` skill (and the orchestrator's discovery blurb) only knew
|
|
14
|
+
the legacy `faststore cms-sync` → Headless CMS flow. On FastStore v4 today
|
|
15
|
+
Headless CMS is LEGACY; the current content path is the **Content Platform**
|
|
16
|
+
(`vtex content` / `yarn cms:content` to upload schemas), and real content
|
|
17
|
+
previews locally via **`/api/preview`** against a CP branch. Corrected both
|
|
18
|
+
files to lead with CP (legacy path kept, labeled), and clarified that
|
|
19
|
+
`faststore dev` runs locally with **no** account access — only real CONTENT
|
|
20
|
+
needs the account, not the app. Fixes misleading "faststore needs cms-sync to
|
|
21
|
+
render" guidance. (Skill/knowledge only; `porter`/`triager` inherit it via
|
|
22
|
+
`target_skill_path` — no agent change.)
|
|
23
|
+
|
|
24
|
+
## [0.25.0] — 2026-08-20
|
|
25
|
+
|
|
26
|
+
### Added
|
|
27
|
+
|
|
28
|
+
* **Stacked-PR fix mode (`budget.stackPrs`).** The `fix` phase can now chain fix
|
|
29
|
+
PRs instead of merging them: each fix branches off the PREVIOUS fix's branch
|
|
30
|
+
(`fixer` takes a `base_branch` and opens the PR with `gh pr create --base`), so
|
|
31
|
+
the **top of the stack accumulates every fix and its per-PR preview deploy
|
|
32
|
+
shows all fixes together** — one combined preview to review before landing
|
|
33
|
+
anything. Nothing is merged; a new `stack-review` terminal reports the ordered
|
|
34
|
+
stack + the top PR's preview URL and hands off (merge bottom-up, delete
|
|
35
|
+
branches last). Default stays **merge mode** (independent PRs off `main`, one
|
|
36
|
+
at a time, with the `fix → parity` re-score loop). Set at `discovery` when the
|
|
37
|
+
user asks to stack fixes / see one preview with all fixes / not auto-merge.
|
|
38
|
+
Orchestration-only change — no CLI behavior change (version kept in lockstep).
|
|
39
|
+
|
|
8
40
|
## [0.24.0] — 2026-08-20
|
|
9
41
|
|
|
10
42
|
### Added
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@decocms/parity",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.25.1",
|
|
4
4
|
"description": "E2E parity validator for site migrations. Compares prod vs cand and reports UI, functional, SEO, visual, and Web Vitals deltas with an LLM-ranked HTML report.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"license": "MIT",
|