@smart-cloud/publisher-exporter 1.1.73 → 1.1.75
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 +17 -0
- package/dist/content-sync.js +15 -15
- package/dist/crawl.js +13 -13
- package/dist/deploy.js +6 -6
- package/dist/invalidate.js +1 -1
- package/dist/queue-runner.js +1 -1
- package/package.json +1 -1
- package/publisher.config.example.json +3 -0
package/README.md
CHANGED
|
@@ -6,6 +6,23 @@ It is designed to run outside WordPress. The WordPress plugin only manages runti
|
|
|
6
6
|
|
|
7
7
|
## Release notes
|
|
8
8
|
|
|
9
|
+
### 1.1.75
|
|
10
|
+
|
|
11
|
+
- Replace inherited remote-workspace objects when an incremental S3-native crawl produces a changed coordinator-owned output, including sitemap XML files.
|
|
12
|
+
- Keep Lambda outputs created by the current job authoritative, so local files cannot overwrite freshly rendered pages or remotely fetched assets.
|
|
13
|
+
- Add regression coverage for a changed sitemap inherited from a previous remote export manifest and for current-job object preservation.
|
|
14
|
+
|
|
15
|
+
Upgrade the external coordinator before the next incremental publish. Existing stale sitemap objects are not repaired automatically; run a new incremental publish after upgrading. Pinning the same exporter version in the Lambda worker image is supported for release parity, but this fix changes coordinator staging only.
|
|
16
|
+
|
|
17
|
+
### 1.1.74
|
|
18
|
+
|
|
19
|
+
- Add an opt-in, fail-closed WordPress page-cache purge preflight for crawl-like jobs. The coordinator authenticates with the existing private runtime token and accepts only an explicit complete-purge confirmation from the source site.
|
|
20
|
+
- Run the purge after invalidating the deploy plan and marking the crawl incomplete, but before deleting or writing export output. Authentication, transport, redirect, status, response-shape, or provider failures stop the crawl and preserve the previous files.
|
|
21
|
+
- Cover publish, crawl, retry-timeouts, single-URL, and content-sync jobs that enter rendering. Deploy-only, CDN-invalidation-only, and rewrite-resume operations do not purge.
|
|
22
|
+
- Keep the exporter cache-vendor-neutral. WordPress delegates to a versioned provider contract supplied by the host integration; the exporter contains no WP Super Cache, Cache Enabler, Nginx, or hosting-vendor implementation.
|
|
23
|
+
|
|
24
|
+
The preflight is disabled by default. Enable it only after installing and testing a source-site adapter. A complete purge makes the first request for every unique URL a cache miss; it guarantees freshness and repopulates the cache for later visitors or retries, but it is not a separate cache-warming phase.
|
|
25
|
+
|
|
9
26
|
### 1.1.73
|
|
10
27
|
|
|
11
28
|
- 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).
|