@smart-cloud/publisher-exporter 1.1.70 → 1.1.72
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 +20 -0
- package/dist/content-sync.js +15 -15
- package/dist/crawl.js +13 -13
- package/dist/remote-worker.js +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -4,6 +4,26 @@
|
|
|
4
4
|
|
|
5
5
|
It is designed to run outside WordPress. The WordPress plugin only manages runtime config, queue state, and logs.
|
|
6
6
|
|
|
7
|
+
## Release notes
|
|
8
|
+
|
|
9
|
+
### 1.1.72
|
|
10
|
+
|
|
11
|
+
- Correct the coordinator's saved-page counter for HTML already uploaded to the S3 workspace by Lambda workers.
|
|
12
|
+
- Include validated retained local or remote outputs when incremental processing reuses a page, and when a completed checkpoint is resumed. Count each output path once per run, including repeated writes or retries.
|
|
13
|
+
- Keep failed requests, rejected URLs, missing outputs, and unrelated skips out of the saved-page count. Rendering, reuse decisions, asset processing, and deployment behavior are unchanged.
|
|
14
|
+
- Add behavioral regression coverage for local and S3-native saves, reuse, checkpoints, failures, and duplicate output accounting.
|
|
15
|
+
|
|
16
|
+
The counter correction takes effect in new coordinator jobs after upgrading the exporter. It does not modify an already running job or retrospectively rewrite its progress log.
|
|
17
|
+
|
|
18
|
+
### 1.1.71
|
|
19
|
+
|
|
20
|
+
- Restore `--no-zygote` for Lambda Chromium launches while keeping `--single-process` disabled. Browser and renderer processes remain separate.
|
|
21
|
+
- Retain one reusable browser per render batch and a fresh, non-persistent browser context for each page. Cookies and browser storage do not carry over between pages; the browser closes and its owned temporary files are cleaned at the batch boundary.
|
|
22
|
+
- Test the actual Playwright Headless Shell instead of substituting full Chromium. The lifecycle check runs three batches of 20 pages, verifies context isolation, samples browser-tree memory and temporary storage, and invokes the production temporary-file cleanup between batches.
|
|
23
|
+
- Validate the corrected launch configuration in an isolated ARM64 Lambda: 62 rendered pages across 11 invocations in the same warm execution environment. Local smoke tests remain additional checks, not a substitute for Lambda validation.
|
|
24
|
+
|
|
25
|
+
Upgrade the Lambda image's pinned exporter version to `1.1.71` and redeploy the worker stack. Updating only the WordPress coordinator's npm package does not update existing Lambda images. No architecture change is required.
|
|
26
|
+
|
|
7
27
|
## Install
|
|
8
28
|
|
|
9
29
|
Global install:
|