Static Publisher v1.0.23 – Lambda data plane

Summary

Static Publisher 1.0.23 moves the heavy export phases into the Lambda data plane and simplifies their administration.

Rendered HTML and downloaded assets can remain in the S3 workspace throughout discovery, rewriting, and deployment. The WordPress-side exporter acts as a lightweight coordinator responsible for URL queues, policy decisions, compact manifests, retries, logs, and terminal job state.

S3-native Lambda processing

• Add a dedicated asset worker for downloading discovered resources directly into the S3 workspace.
• Discover dependent assets and additional URLs from Lambda-rendered HTML.
• Rewrite workspace objects in place without downloading the complete export to the coordinator.
• Deploy completed exports directly from the workspace bucket to the configured target.
• Keep render, asset, rewrite, and deploy phases explicit and independently observable.
• Fail delegated phases explicitly when their worker or result is unavailable; no silent local fallback is performed.

Unified processing controls

• Replace separate local and per-Lambda concurrency fields with one Processing concurrency control.
• Replace separate phase delegation switches with one Delegate processing to Lambda switch.
• Use the same concurrency value for local workers and the requested Lambda fan-out.
• Clarify that the configured value is not an account-wide Lambda concurrency limit.
• Preserve existing mixed legacy settings until an administrator explicitly changes the corresponding unified control.
• Use an incrementable number control that can remain temporarily empty while editing and normalizes to the supported 1–100 range when focus leaves the field.
• Improve spacing between the concurrency description and its input.