@smart-cloud/publisher-exporter 1.2.12 → 1.2.14

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
@@ -499,6 +499,17 @@ npx @smart-cloud/publisher-exporter queue-runner --runtime-dir /srv/site/runtime
499
499
 
500
500
  Use `--resume-rewrite` when the already exported output is otherwise valid but the rewrite logic changed or a previous crawl stopped during the rewrite phase. This is the fastest repair path for stale output caused by rewrite-only bugs such as escaped JSON replacement issues, protocol-relative asset URLs like `//host/path.css`, or an interrupted final rewrite.
501
501
 
502
+ Profile-bound manifests use a versioned output compatibility fingerprint. Changes
503
+ to logging, the AWS profile name, concurrency, or remote batch/retry counts do not
504
+ by themselves require a full rebuild. Source, destination, binding, rewrite,
505
+ discovery, rendering timing and unknown configuration fields remain protected.
506
+ An older manifest can adopt the new fingerprint during a normal successful run
507
+ with its original configuration; an already changed legacy configuration still
508
+ requires a full rebuild because its old hash cannot prove which settings changed.
509
+ Updating the exporter installation path or package version alone does not change
510
+ this fingerprint. Follow each release's compatibility requirements when an
511
+ exporter algorithm changes, and retain the previous installation for rollback.
512
+
502
513
  For an interrupted rewrite with otherwise unchanged rules, prefer
503
514
  `crawl --resume-rewrite --pending-only`. It selects only manifest outputs whose
504
515
  `rewriteComplete` is not true, including text assets; aliases sharing one path