@smart-cloud/publisher-exporter 1.2.6 → 1.2.7

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
@@ -41,6 +41,22 @@ manifests. The declaration does not require longer render readiness waits.
41
41
 
42
42
  ## Release notes
43
43
 
44
+ ### 1.2.7
45
+
46
+ - Add `crawl --resume-rewrite --pending-only` to process only unfinished page
47
+ and text-asset outputs from the manifest, deduplicated by output path. It
48
+ does not enumerate or rewrite the rest of the export tree. Plain
49
+ `--resume-rewrite` retains its all-text-file behavior for changed rewrite rules.
50
+ - Add `--rewrite-concurrency <1..100>` as a per-run override for local rewrite
51
+ workers, applied after normal configuration defaults. The default continues
52
+ to use configured parallelism; lowering the worker count trades speed for
53
+ available CPU capacity for other work.
54
+ - Avoid constructing literal URL matchers when the source literal is absent,
55
+ and skip JSON-context URL escaping setup in files without script/meta tags.
56
+ Replacement order and URL boundary checks remain unchanged.
57
+ - Update only the host exporter for these options. No WordPress plugin or
58
+ Lambda stack update is required.
59
+
44
60
  ### 1.2.6
45
61
 
46
62
  - Local rewrite resume tracks manifest completion and preserves pending deploy
@@ -464,6 +480,13 @@ npx @smart-cloud/publisher-exporter queue-runner --runtime-dir /srv/site/runtime
464
480
 
465
481
  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.
466
482
 
483
+ For an interrupted rewrite with otherwise unchanged rules, prefer
484
+ `crawl --resume-rewrite --pending-only`. It selects only manifest outputs whose
485
+ `rewriteComplete` is not true, including text assets; aliases sharing one path
486
+ are processed once. No pending files means no text files are scanned. A
487
+ `Checked unchanged` message means the selected file was read and its rewrite
488
+ result was byte-identical; its pending flag can still be completed safely.
489
+
467
490
  The manifest is updated only after the whole rewrite phase succeeds, for paths
468
491
  whose rewrite callbacks completed. Entries sharing a completed path are marked
469
492
  complete together; missing or empty files remain incomplete with warnings. A