@smart-cloud/publisher-exporter 1.2.4 → 1.2.6

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,29 @@ manifests. The declaration does not require longer render readiness waits.
41
41
 
42
42
  ## Release notes
43
43
 
44
+ ### 1.2.6
45
+
46
+ - Local rewrite resume tracks manifest completion and preserves pending deploy
47
+ changes. It rejects an S3-native export manifest before mutation; workspace
48
+ objects are authoritative and cannot use local rewrite completion flags.
49
+ This coordinator-only change requires no Lambda, plugin, or IAM change.
50
+
51
+ ### 1.2.5
52
+
53
+ - Expand a queued URL job's `urls` array into repeated `--url` arguments for one
54
+ crawl invocation and one deploy plan. Retain legacy single `url` jobs. The
55
+ admin accepts one URL/path per line; PHP and the runner validate list types,
56
+ blank lines, duplicates, control characters and filesystem-prefix rejection,
57
+ up to 500 unique URLs and 64 KiB of combined UTF-8 URL text.
58
+ - Forward the optional boolean `refreshAssets` queue field as `--refresh-assets`
59
+ for URL and retry-timeouts jobs. Omitted or false retains default asset reuse;
60
+ other job types never receive the flag. The WordPress 1.2.2 job controls expose
61
+ this per-job choice as "Download assets again for this job".
62
+ - Update the WordPress plugin and host queue-runner exporter together to use
63
+ the new checkbox. Direct CLI use of `--refresh-assets` remains supported.
64
+ This patch changes no Lambda worker handler or browser dependency; a worker
65
+ stack rebuild is not required for the queue forwarding change.
66
+
44
67
  ### 1.2.4
45
68
 
46
69
  - Restrict retry crawls to their initial failure URL list. Links discovered by
@@ -436,12 +459,21 @@ npx @smart-cloud/publisher-exporter queue-runner --runtime-dir /srv/site/runtime
436
459
  - `crawl` without extra flags performs a normal full crawl, asset download, and final text rewrite.
437
460
  - `crawl --crawl-mode incremental` reuses the existing crawl manifest when possible and rewrites only the files affected by re-crawled pages, text assets, or changed asset-map entries. After a successful unlimited discovery pass it also removes exporter-generated HTML that is no longer present in the current manifest and records exact deletion tombstones for the deploy step. Post-crawl copy-map destinations remain protected.
438
461
  - An incremental crawl now fails closed when the remote WP Suite subscription configuration cannot be loaded. It never silently falls back to a full crawl that clears the existing output tree.
439
- - `crawl --resume-rewrite` skips discovery, rendering, and asset download, then reruns the final text rewrite over the existing output tree using the current rewrite rules.
462
+ - `crawl --resume-rewrite` skips discovery, rendering, and asset download, then rewrites existing nonempty text files using the current rewrite rules. It does not purge the page cache.
440
463
  - `crawl --retry-timeouts` retries timed-out URLs from the latest archived full crawl or publish log snapshot.
441
464
 
442
465
  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.
443
466
 
444
- If you need to repair existing exported HTML after a rewrite bug, prefer `--resume-rewrite` over a new incremental crawl. Incremental crawl only rewrites targeted files; `--resume-rewrite` reprocesses every text file in the current output.
467
+ The manifest is updated only after the whole rewrite phase succeeds, for paths
468
+ whose rewrite callbacks completed. Entries sharing a completed path are marked
469
+ complete together; missing or empty files remain incomplete with warnings. A
470
+ rewrite failure retains the incomplete marker and prior deploy plan. Successful
471
+ resume carries pending changes forward and includes previously incomplete files
472
+ that completed, even if their bytes did not change. The `rewrite-resume` plan
473
+ suppresses deletions and does not establish a content-sync baseline. It targets
474
+ changed files unless an earlier pending plan requires a full sync.
475
+
476
+ If you need to repair existing exported HTML after a rewrite bug, prefer `--resume-rewrite` over a new incremental crawl. Incremental crawl only rewrites targeted files; `--resume-rewrite` processes existing nonempty text files in the current output.
445
477
 
446
478
  During `--resume-rewrite`, the terminal can be quieter than a full crawl. Progress still updates in `runtime/current-progress.json` and the live crawl event snapshot under the configured log directory.
447
479
 
@@ -696,7 +728,7 @@ enabled remote phase.
696
728
 
697
729
  ## Troubleshooting
698
730
 
699
- - If exported HTML still contains old rewritten URLs after a rewrite fix, run `crawl --resume-rewrite`. This reprocesses every text file in the current output tree and does not depend on earlier `rewriteComplete: true` entries in `crawl-manifest.json`.
731
+ - If exported HTML still contains old rewritten URLs after a rewrite fix, run `crawl --resume-rewrite`. This reprocesses existing nonempty text files in the current output tree and does not depend on earlier `rewriteComplete: true` entries in `crawl-manifest.json`.
700
732
  - If `--resume-rewrite` appears to stop after the initial resume message, check `runtime/current-progress.json` and `<logDir>/current-crawl-event.json` before assuming it is stuck. That phase can stay mostly quiet on stdout while it rewrites files.
701
733
  - If direct CLI execution seems to ignore the expected runtime state, verify that `PUBLISHER_CONFIG` and `STATIC_PUBLISHER_RUNTIME_DIR` both point at the same runtime tree. A mismatched config path and runtime dir can make the run look idle or incomplete.
702
734
  - Prefer incremental crawl when the existing manifest is trusted and you only need a fast recrawl of changed pages or assets. Prefer a full crawl when discovery rules changed, the manifest is missing or suspect, or you want a clean end-to-end rebuild.