@smart-cloud/publisher-exporter 1.1.77 → 1.1.79

package/README.md

@@ -6,6 +6,21 @@ It is designed to run outside WordPress. The WordPress plugin only manages runti
 
 ## Release notes
 
+### 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.
+- Apply the guard through the shared serializer used by local rendering, delegated Lambda rendering, timeout fallback capture, and partial recovery capture.
+- Add regression coverage for the generic runtime-marker sanitizer and shared local/remote capture path.
+
+Upgrade both the external coordinator and every delegated render-worker image to `1.1.78`, then run a full publish. Existing static HTML retains stale runtime markers until the affected pages are rendered and deployed again.
+
 ### 1.1.77
 
 - Report delegated rewrite progress as monotonic job-wide file and completed-batch totals, even when concurrent Lambda batches finish out of order.