@smart-cloud/publisher-exporter 1.1.81 → 1.1.83
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 +9 -0
- package/dist/content-sync.js +15 -15
- package/dist/crawl.js +13 -13
- package/dist/deploy.js +5 -5
- package/dist/remote-worker.js +5 -5
- package/dist/rewrite-worker.js +2 -2
- package/package.json +3 -3
package/README.md
CHANGED
|
@@ -6,6 +6,15 @@ It is designed to run outside WordPress. The WordPress plugin only manages runti
|
|
|
6
6
|
|
|
7
7
|
## Release notes
|
|
8
8
|
|
|
9
|
+
### 1.1.82
|
|
10
|
+
|
|
11
|
+
- Buffer cross-account S3 upload streams into 64 KiB chunks before the AWS SDK applies streaming checksums. This prevents real HTML and asset bodies from failing with `Only the last chunk is allowed to have a size less than 8192 bytes` while preserving bounded streaming instead of loading complete objects into Lambda memory.
|
|
12
|
+
- Keep deploy-only recovery on the existing remote export manifest: after updating delegated workers, rerun only the deploy job to copy the already rendered and rewritten workspace objects without another crawl.
|
|
13
|
+
- Make relative URL rewriting atomic and repeatable. Overlapping absolute, root-relative, escaped, and protocol-relative rules no longer rewrite output produced by an earlier rule or add another `../` prefix when a file passes through more than one rewrite phase.
|
|
14
|
+
- Remove nested browser-runtime DOM before serializing rendered pages, not only top-level runtime roots. Authored placeholders and bootstrap scripts remain, so React, Mantine, Stripe, and similar client integrations initialize exactly once on the published page instead of duplicating pre-rendered controls.
|
|
15
|
+
|
|
16
|
+
Upgrade the orchestrator and delegated workers to `1.1.82`. A WordPress plugin update is not required. A deploy-only retry is sufficient for the cross-account S3 upload failure; sites affected by malformed relative URLs or serialized runtime UI need a full publish so every affected HTML page is rewritten or rendered from its authored source.
|
|
17
|
+
|
|
9
18
|
### 1.1.81
|
|
10
19
|
|
|
11
20
|
- Let the base deployment target and each named deployment profile select an optional AWS shared-config profile for local S3 deployment and CloudFront invalidation. One-time credentials attached to a queued job still take precedence, and only the profile name is stored in Publisher configuration.
|