@smart-cloud/publisher-exporter 1.2.1 → 1.2.2

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 CHANGED
@@ -41,6 +41,43 @@ manifests. The declaration does not require longer render readiness waits.
41
41
 
42
42
  ## Release notes
43
43
 
44
+ ### 1.2.2
45
+
46
+ - Save the original main HTTP response HTML in both local and delegated
47
+ rendering, including generated 404 pages. Browser DOM mutations, runtime
48
+ mounts, tokens and transient UI are never serialized into published HTML.
49
+ Normal URL rewriting still runs on the saved source HTML afterward.
50
+ - Remove DOM serialization fallbacks, partial-DOM recovery saves and runtime
51
+ mount snapshotting from the publishing paths. If the response body cannot be
52
+ read, retry or fail the page instead of substituting different content. Read
53
+ the response belonging to that navigation; do not issue a second page GET.
54
+ - Keep browser execution for DOM/network asset discovery and dynamically created
55
+ page links. Saving source HTML does not disable discovery inside shadow roots,
56
+ declared dependencies or JavaScript-generated links and resources.
57
+ - Retain the main HTTP response independently of `page.goto()` completion.
58
+ A synchronous script in the document head can keep the browser parser from
59
+ creating the body even when the complete source HTML has arrived.
60
+ - Before browser discovery, require a parsed HTML document with a body within
61
+ the configured readiness timeout. A navigation timeout can recover if parsing
62
+ finishes within that budget; it does not cause a partial-DOM export.
63
+ A zero or invalid readiness timeout uses a bounded 1.5-second document check
64
+ instead of disabling this mandatory check.
65
+ - Retry failed navigation or document readiness up to three times, closing the
66
+ failed page and context before a one-second, then two-second backoff. Ordinary
67
+ HTTP 404 skipping, generated 404 capture and HTTP 5xx retries remain separate.
68
+ - Log the response status, document readiness and grouped pending-request origins
69
+ and resource types. Pending-request diagnostics omit paths, query strings,
70
+ credentials and headers. Persistent failures retain the incomplete-crawl
71
+ deployment barrier and never save an empty successful page.
72
+
73
+ Upgrade the coordinator and rebuild delegated worker images with 1.2.2 after
74
+ active jobs stop. Node.js, Playwright, browser launch flags, WordPress plugins
75
+ and cache adapters are unchanged; this patch alone does not require reinstalling
76
+ browser binaries or changing the worker protocol. Run crawl/publish afterward;
77
+ deploy alone cannot finish a failed render. Use a full publish once to replace
78
+ all previously saved DOM-based HTML: incremental mode can reuse existing
79
+ unchanged outputs and does not automatically convert their capture format.
80
+
44
81
  ### 1.2.1
45
82
 
46
83
  - Serialize a detached document clone instead of destructively cleaning the