@smart-cloud/publisher-exporter 1.1.71 → 1.1.73
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 +21 -0
- package/dist/content-sync.js +15 -15
- package/dist/crawl.js +13 -13
- package/package.json +3 -2
package/README.md
CHANGED
|
@@ -6,6 +6,27 @@ It is designed to run outside WordPress. The WordPress plugin only manages runti
|
|
|
6
6
|
|
|
7
7
|
## Release notes
|
|
8
8
|
|
|
9
|
+
### 1.1.73
|
|
10
|
+
|
|
11
|
+
- Retry page-render responses with HTTP 500–599 instead of silently skipping them. The coordinator applies a bounded 5/10/20/30-second backoff without increasing worker concurrency. Local rendering allows three attempts; delegated rendering retains `remoteWorkers.render.maxAttempts` (default two, supported range one to five).
|
|
12
|
+
- Retry only failed URLs in a remote batch, retain successful pages, and never register a 5xx error document as exported HTML. Local retries close their failed page/context before waiting and create a fresh context for the next attempt.
|
|
13
|
+
- Record exhausted HTTP retries as errors with URL, status and attempt count. An unresolved page 5xx leaves the crawl incomplete and blocks rewrite/deploy-plan creation and subsequent deployment, including full publishes.
|
|
14
|
+
- Preserve normal 4xx skip/tombstone handling and generated 404 capture. Asset/sitemap HTTP policies and `--retry-timeouts` selection are unchanged; this patch addresses page-render responses.
|
|
15
|
+
- Add mixed-batch, retry-budget, error-body, cleanup, progress-counter and incomplete-export regression coverage.
|
|
16
|
+
|
|
17
|
+
Run `npm run verify:page-http-retry` for an isolated local HTTP-server/headless-Chromium integration test, or `npm run build:premium && npm run verify:page-http-retry -- --built` to test the distributable CLI. The check makes no AWS or WordPress production changes.
|
|
18
|
+
|
|
19
|
+
Upgrade the external coordinator after active jobs finish. Existing skipped pages are not repaired automatically: crawl the affected URLs again or run a new publish. This is a coordinator-only change; no Lambda browser configuration, handler or infrastructure change is required. The existing retry-timeouts mode does not select HTTP 5xx errors.
|
|
20
|
+
|
|
21
|
+
### 1.1.72
|
|
22
|
+
|
|
23
|
+
- Correct the coordinator's saved-page counter for HTML already uploaded to the S3 workspace by Lambda workers.
|
|
24
|
+
- 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.
|
|
25
|
+
- 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.
|
|
26
|
+
- Add behavioral regression coverage for local and S3-native saves, reuse, checkpoints, failures, and duplicate output accounting.
|
|
27
|
+
|
|
28
|
+
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.
|
|
29
|
+
|
|
9
30
|
### 1.1.71
|
|
10
31
|
|
|
11
32
|
- Restore `--no-zygote` for Lambda Chromium launches while keeping `--single-process` disabled. Browser and renderer processes remain separate.
|