@smart-cloud/publisher-exporter 1.1.87 → 1.2.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/README.md +33 -0
- package/dist/content-sync.js +15 -15
- package/dist/crawl.js +13 -13
- package/dist/deploy.js +6 -6
- package/dist/invalidate.js +3 -3
- package/dist/queue-runner.js +3 -3
- package/dist/remote-worker-health.js +1 -1
- package/dist/remote-worker.js +5 -5
- package/dist/rewrite-worker.js +2 -2
- package/package.json +3 -3
package/README.md
CHANGED
|
@@ -41,6 +41,39 @@ manifests. The declaration does not require longer render readiness waits.
|
|
|
41
41
|
|
|
42
42
|
## Release notes
|
|
43
43
|
|
|
44
|
+
### 1.2.1
|
|
45
|
+
|
|
46
|
+
- Serialize a detached document clone instead of destructively cleaning the
|
|
47
|
+
live browser page. Preserve the HTML/head/body scaffold even when scripts
|
|
48
|
+
created it, and restore structural runtime mounts from their pristine
|
|
49
|
+
snapshots rather than deleting them.
|
|
50
|
+
- Continue removing transient runtime roots, overlays, initialization markers
|
|
51
|
+
and scroll locks from exported HTML without changing the live DOM or running
|
|
52
|
+
custom-element constructors during snapshot restoration. Repeated captures
|
|
53
|
+
produce the same result.
|
|
54
|
+
- Reject missing-body and non-HTML documents with explicit serialization
|
|
55
|
+
diagnostics. Do not hide an incomplete render with optional chaining or
|
|
56
|
+
manufacture an empty successful export; the incomplete-crawl deploy barrier
|
|
57
|
+
remains enforced.
|
|
58
|
+
|
|
59
|
+
Upgrade the coordinator after active jobs stop. Delegated render workers use
|
|
60
|
+
the same serializer and need an image rebuild to receive this correction.
|
|
61
|
+
Node 24.22.1 and Playwright 1.63.0 remain unchanged, so a browser reinstall is
|
|
62
|
+
not required solely for this patch. No WordPress plugin update is needed.
|
|
63
|
+
|
|
64
|
+
A failure at HTML capture is still a crawl failure, not a deploy failure.
|
|
65
|
+
Run a new crawl/publish after upgrading. An incremental crawl can reuse
|
|
66
|
+
successfully checkpointed outputs when the existing manifest and change
|
|
67
|
+
tokens permit it; a failed full crawl may not have such checkpoints. Do not
|
|
68
|
+
use `--resume-rewrite` or delete the incomplete marker to bypass unfinished
|
|
69
|
+
rendering, asset discovery/downloads or rewrite.
|
|
70
|
+
|
|
71
|
+
Release audit: the production high-severity gate passes. Two inherited low
|
|
72
|
+
findings refer to [deepmerge GHSA-gcqx-w48m-w2h4](https://github.com/advisories/GHSA-gcqx-w48m-w2h4)
|
|
73
|
+
through `@wordpress/data`; no patched deepmerge version is currently published.
|
|
74
|
+
This targeted hotfix does not apply npm's suggested breaking WordPress package
|
|
75
|
+
downgrade, and does not claim a zero-finding audit.
|
|
76
|
+
|
|
44
77
|
### 1.1.87
|
|
45
78
|
|
|
46
79
|
- Require patched supported Node.js runtimes: Node 22.23.4 or newer within
|