@smart-cloud/publisher-exporter 1.2.18 → 1.3.0

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 CHANGED
@@ -39,8 +39,39 @@ coordinator and delegated workers before relying on these declarations, purge
39
39
  stale source page caches, and recrawl affected pages to update existing
40
40
  manifests. The declaration does not require longer render readiness waits.
41
41
 
42
+ ## Configuration changes and publishing
43
+
44
+ | Change | Required operation |
45
+ | --- | --- |
46
+ | Logging, concurrency, worker batch size or retry count | No full crawl; output compatibility is unchanged. |
47
+ | First generated 404 capture, appended seed paths or appended sitemap roots | Normal unlimited Incremental publish, without resume, with complete Lambda delegation and a verified previous export. |
48
+ | Rendering/readiness, URL rewriting, filters, output destination, other unknown settings, discovery removal/reordering, replacing/disabling an existing 404 capture | Full unlimited publish without resume. Profile bindings and target ownership must still match. |
49
+
50
+ Incremental discovery changes retain existing workspace objects. The new 404 must be freshly rendered from a real HTTP 404 response. Added sitemap trees and required outputs must succeed before the new configuration becomes deployable. Targeted URL/retry/resume or deploy-only commands cannot approve a configuration transition. Unknown fields and scalar types remain significant; operational fields alone do not require regeneration.
51
+
52
+ Manifests store per-setting hashes and public discovery settings for future comparisons, excluding rotating render headers/runtime tokens. Older v2 manifests can recover metadata from up to 100 immutable job snapshots only when their profile binding and complete output fingerprint match exactly. These historical reads make no network calls and write no configuration or manifest. Without matching history, only the exact first-404 inverse is supported; otherwise a Full publish establishes a new baseline.
53
+
42
54
  ## Release notes
43
55
 
56
+ ### 1.3.0
57
+
58
+ - Add local rendering for Commerce-protected WordPress pages and media. Set
59
+ `SMARTCLOUD_COMMERCE_PUBLISHER_SECRET` in the Exporter process and enable
60
+ authenticated Publisher renders on the source site.
61
+ - Exchange the source credential for a short lease scoped to the exact HTTPS
62
+ origin and configured routes. The Exporter renews the lease during the crawl
63
+ and releases it on exit. Select `--local-render` when Lambda rendering is enabled.
64
+ - Require proof of authorized rendering for each protected response. An
65
+ incomplete protected export blocks deployment. Configure the destination
66
+ to enforce the same access groups before publishing.
67
+
68
+ ### 1.2.19
69
+
70
+ - Separate operational, incrementally supported discovery and full-rebuild configuration changes.
71
+ - Add generated 404 captures and append seed/sitemap discovery without discarding the verified export. Require successful new captures and sitemap trees before deployment.
72
+ - Recover compatibility metadata from verified immutable job history, and identify changed settings in rebuild errors.
73
+ - Preserve existing profile/target, failure, incomplete-crawl and direct-deploy guards.
74
+
44
75
  ### 1.2.18
45
76
 
46
77
  - Report profile worker failures with a stable error code, operation, configured