@smart-cloud/publisher-exporter 1.2.17 → 1.2.19
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 +32 -0
- package/dist/cli.js +1 -1
- package/dist/content-sync.js +16 -16
- package/dist/crawl.js +14 -14
- package/dist/deploy.js +6 -6
- package/dist/invalidate.js +1 -1
- package/dist/queue-runner.js +2 -2
- package/dist/remote-worker-health.js +1 -1
- package/dist/remote-worker.js +6 -6
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -39,8 +39,40 @@ 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.2.19
|
|
57
|
+
|
|
58
|
+
- Separate operational, incrementally supported discovery and full-rebuild configuration changes.
|
|
59
|
+
- Add generated 404 captures and append seed/sitemap discovery without discarding the verified export. Require successful new captures and sitemap trees before deployment.
|
|
60
|
+
- Recover compatibility metadata from verified immutable job history, and identify changed settings in rebuild errors.
|
|
61
|
+
- Preserve existing profile/target, failure, incomplete-crawl and direct-deploy guards.
|
|
62
|
+
|
|
63
|
+
### 1.2.18
|
|
64
|
+
|
|
65
|
+
- Report profile worker failures with a stable error code, operation, configured
|
|
66
|
+
Lambda alias/region, running exporter version, missing capabilities and a
|
|
67
|
+
concrete recovery action. Preserve safe AWS error codes and request/task IDs
|
|
68
|
+
without exposing signed requests, credentials or raw worker payloads.
|
|
69
|
+
- Preserve the original worker failure if updating its progress record also
|
|
70
|
+
fails. Carry diagnostics through crawl/deploy logs and queue failure summaries.
|
|
71
|
+
- Update both the coordinator package and the Lambda workers referenced by the
|
|
72
|
+
current backend profile. Updating another stack or the legacy runtime's
|
|
73
|
+
remote-workers.json does not update a profile-bound deployment. Existing crawl
|
|
74
|
+
outputs and incremental reuse remain available after a deploy-only failure.
|
|
75
|
+
|
|
44
76
|
### 1.2.8
|
|
45
77
|
|
|
46
78
|
- Add revision-bound backend profile handoff with isolated queues, captured
|