@smart-cloud/publisher-exporter 1.1.78 → 1.1.80

package/README.md

@@ -6,6 +6,21 @@ It is designed to run outside WordPress. The WordPress plugin only manages runti
 
 ## Release notes
 
+### 1.1.80
+
+- Remove client-created top-level provider, portal, and overlay roots before serializing rendered HTML, including roots mounted through a bundled direct `react-dom/client` import that is not observable through `window.ReactDOM`.
+- Ensure published pages run their parser-authored bootstrap and create fresh client providers instead of mistaking serialized, listener-free DOM for a live mount.
+- Add a real headless Chromium regression test that reproduces the provider marker, captures the page, reloads the serialized HTML, and verifies successful provider reinitialization.
+
+Upgrade both the external coordinator and delegated render-worker image to `1.1.80`, then rerender affected HTML pages. This is an exporter-only fix; no WordPress plugin update is required.
+
+### 1.1.79
+
+- Let targeted content-sync trust pages already recorded in the verified baseline manifest even when the prior local render workspace has been cleaned up after a successful publish.
+- Keep strict sitemap coverage checks for URLs that are absent from the verified baseline; newly published pages remain queued until a later normal publish establishes their deployable output.
+
+This is a coordinator-only fix. Upgrade and restart the external queue runner; delegated Lambda render workers do not need an update for this release.
+
 ### 1.1.78
 
 - Remove serialized runtime-only `data-*-bound`, `data-*-initialized`, `data-*-mounted`, and `data-*-hydrated` markers before saving rendered HTML. Event listeners and in-memory framework instances cannot survive HTML serialization, so retaining those markers can suppress clean initialization on the published origin.