@smart-cloud/publisher-exporter 1.1.84 → 1.1.86

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,51 @@ manifests. The declaration does not require longer render readiness waits.
41
41
 
42
42
  ## Release notes
43
43
 
44
+ ### 1.1.86
45
+
46
+ - Share CSS asset discovery between the coordinator and delegated workers.
47
+ JavaScript URL constructors and variable expressions no longer become
48
+ fictitious relative asset paths. Preserve real CSS URLs and imports,
49
+ static CSS embedded in JavaScript literals, declared shadow-root assets
50
+ and existing lazy JavaScript chunk discovery. No customer-specific
51
+ exclusions or blanket filename/extension restrictions are introduced.
52
+ - Check expected outputs from saved pages, current-run manifest entries and
53
+ changed files instead of treating every completed or skipped request as a
54
+ successful output. Real missing outputs still warn, remote-only S3 outputs
55
+ remain valid and conservative deletion protection stays intact.
56
+
57
+ Update the VM coordinator and delegated Lambda worker images to `1.1.86`.
58
+ No WordPress plugin update or new CDK resource is required. The corrected
59
+ missing-output check applies to the next incremental crawl. Run a full publish
60
+ once to rebuild dependency metadata if an existing manifest already contains
61
+ spurious dependencies: unchanged assets reused incrementally can retain their
62
+ previously discovered dependency lists.
63
+
64
+ ### 1.1.85
65
+
66
+ - Pin Playwright exactly to `1.63.0`, matching the delegated worker browser
67
+ image. Installing the published package into a fresh image can no longer
68
+ silently select a newer Playwright release with incompatible Chromium paths.
69
+ - Fail closed on unrecovered page/worker rendering errors in normal full and
70
+ incremental crawls, not only targeted content-sync or origin HTTP 5xx errors.
71
+ Stop scheduling new pages after a fatal render failure, drain in-flight
72
+ workers, retain the incomplete marker and refuse to create a deploy plan.
73
+ Partial DOM recovery remains diagnostic output, not a completed publication.
74
+ - Export the actual Lambda browser launch options for the container build
75
+ smoke test. The worker build checks the exporter dependency, installed
76
+ Playwright/core and base image version, then launches Chromium and renders
77
+ two isolated contexts before accepting the image.
78
+ - Preserve intentional HTTP 404/410 handling and successful incremental runs
79
+ that reuse all pages without rendering. A zero-render counter alone is not
80
+ considered a failure.
81
+
82
+ Upgrade both the coordinator and the shared Lambda worker stack to `1.1.85`,
83
+ using the updated worker Dockerfiles and their mandatory browser smoke gate.
84
+ The failed `1.1.84` runs may have left empty or incomplete crawl manifests;
85
+ after both upgrades, run a full publish on each affected source site. A new
86
+ Static Publisher WordPress plugin release is not required. Do not redeploy
87
+ the floating-Playwright `1.1.84` image or bypass the incomplete marker.
88
+
44
89
  ### 1.1.84
45
90
 
46
91
  - Discover explicitly declared runtime assets from inert `application/json`
@@ -0,0 +1 @@
1
+ function n(e){return {headless:true,args:["--no-sandbox","--disable-setuid-sandbox","--no-zygote","--disable-gpu"],...e?{proxy:{server:e}}:{}}}export{n as remoteBrowserLaunchOptions};