@smart-cloud/publisher-exporter 1.2.6 → 1.2.8
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 +42 -0
- package/dist/cli.js +7 -2
- package/dist/content-sync.js +16 -16
- package/dist/crawl.js +14 -14
- package/dist/deploy.js +6 -6
- package/dist/invalidate.js +3 -3
- package/dist/queue-runner.js +3 -3
- package/dist/remote-worker-health.js +1 -1
- package/dist/remote-worker.js +6 -6
- package/dist/rewrite-worker.js +2 -2
- package/package.json +3 -1
package/README.md
CHANGED
|
@@ -41,6 +41,41 @@ manifests. The declaration does not require longer render readiness waits.
|
|
|
41
41
|
|
|
42
42
|
## Release notes
|
|
43
43
|
|
|
44
|
+
### 1.2.8
|
|
45
|
+
|
|
46
|
+
- Add revision-bound backend profile handoff with isolated queues, captured
|
|
47
|
+
publishing targets, and matching license/configuration/translation capture.
|
|
48
|
+
- Support profile-bound render, asset, rewrite and deploy-copy Lambda workers
|
|
49
|
+
with verified immutable inputs and matching export manifests. Profile-enabled
|
|
50
|
+
deployments require compatible Hub endpoints and updated workers; updating
|
|
51
|
+
the host npm package alone does not update Lambda images.
|
|
52
|
+
- Preserve completed outputs after individual profile verification failures;
|
|
53
|
+
retry unresolved render pages only for transient errors. Stop stale or
|
|
54
|
+
unauthorized bindings without resubmitting completed pages.
|
|
55
|
+
- Remove redundant WordPress profile checks and coalesce overlapping checks
|
|
56
|
+
within one invocation. Use bounded 30-second checks with one transient retry,
|
|
57
|
+
live Lambda deadline reserves and redacted, classified diagnostics.
|
|
58
|
+
- Reject uploads and deletions under the reserved `static/config/foundation/`
|
|
59
|
+
subtree before mutation. Publish those configuration files separately.
|
|
60
|
+
- Retain schema1 workers and default configuration for deployments without
|
|
61
|
+
backend profiles. Node requirements remain unchanged.
|
|
62
|
+
|
|
63
|
+
### 1.2.7
|
|
64
|
+
|
|
65
|
+
- Add `crawl --resume-rewrite --pending-only` to process only unfinished page
|
|
66
|
+
and text-asset outputs from the manifest, deduplicated by output path. It
|
|
67
|
+
does not enumerate or rewrite the rest of the export tree. Plain
|
|
68
|
+
`--resume-rewrite` retains its all-text-file behavior for changed rewrite rules.
|
|
69
|
+
- Add `--rewrite-concurrency <1..100>` as a per-run override for local rewrite
|
|
70
|
+
workers, applied after normal configuration defaults. The default continues
|
|
71
|
+
to use configured parallelism; lowering the worker count trades speed for
|
|
72
|
+
available CPU capacity for other work.
|
|
73
|
+
- Avoid constructing literal URL matchers when the source literal is absent,
|
|
74
|
+
and skip JSON-context URL escaping setup in files without script/meta tags.
|
|
75
|
+
Replacement order and URL boundary checks remain unchanged.
|
|
76
|
+
- Update only the host exporter for these options. No WordPress plugin or
|
|
77
|
+
Lambda stack update is required.
|
|
78
|
+
|
|
44
79
|
### 1.2.6
|
|
45
80
|
|
|
46
81
|
- Local rewrite resume tracks manifest completion and preserves pending deploy
|
|
@@ -464,6 +499,13 @@ npx @smart-cloud/publisher-exporter queue-runner --runtime-dir /srv/site/runtime
|
|
|
464
499
|
|
|
465
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.
|
|
466
501
|
|
|
502
|
+
For an interrupted rewrite with otherwise unchanged rules, prefer
|
|
503
|
+
`crawl --resume-rewrite --pending-only`. It selects only manifest outputs whose
|
|
504
|
+
`rewriteComplete` is not true, including text assets; aliases sharing one path
|
|
505
|
+
are processed once. No pending files means no text files are scanned. A
|
|
506
|
+
`Checked unchanged` message means the selected file was read and its rewrite
|
|
507
|
+
result was byte-identical; its pending flag can still be completed safely.
|
|
508
|
+
|
|
467
509
|
The manifest is updated only after the whole rewrite phase succeeds, for paths
|
|
468
510
|
whose rewrite callbacks completed. Entries sharing a completed path are marked
|
|
469
511
|
complete together; missing or empty files remain incomplete with warnings. A
|