@smart-cloud/publisher-exporter 1.1.74 → 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 +8 -0
- package/dist/content-sync.js +15 -15
- package/dist/crawl.js +13 -13
- package/dist/deploy.js +6 -6
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -6,6 +6,14 @@ 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
|
+
|
|
9
17
|
### 1.1.74
|
|
10
18
|
|
|
11
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.
|