Static Publisher 1.1.1 – Shared Hub and PHP audit compatibility

Changes

• Bundle Hub 2.6.1 with correctly scoped shared PHP translations and literal configuration-reset messages.
• Preserve existing publishing configuration, permissions, active-job protections and shared runtime ownership.
• Bind content-event and administrative journal table identifiers through WordPress SQL preparation, with real WordPress placeholder-order regression coverage.
• Improve placeholder translation guidance and URL parsing, check ordinary file cleanup, and retain binary log cursors and atomic local Node-runner lock/reset guarantees.
• Keep concise directory upgrade notices while preserving their full historical guidance in the bundled release archive.

Static Publisher 1.1.0 – WP-Admin redesign

Changes

• Static Publishing brings configuration summary, runner/job status and detailed controls onto one product page. The Publish dialog lets administrators select an available task and target while showing inherited AWS-profile information, without rewriting saved configuration. Pro-only tasks respect entitlement availability.
• The integrated page correctly initializes both the publishing dialog and detailed admin interface. Shared navigation and contextual guidance make the installed runner and deployment requirements visible. A separate confirmed reset protects active queue operations and explains which configuration is removed while retaining published files, content, job history and AWS resources.

Static Publisher 1.0.27 – Shared styling settings

Changes

• Include the updated WP Suite General Settings, where administrators can add absolute or site-relative stylesheet URLs alongside WP Suite Theme CSS for supported frontend components.
• Update Publisher dependencies for the shared WP Suite styling contract. Install @smart-cloud/publisher-exporter 1.1.83 on queue-runner hosts and restart the runner after active jobs finish.

Static Publisher 1.0.26 – Deployment identities for multi-account publishing

Changes

Static Publisher 1.0.26 adds explicit AWS shared-config profile selection for deployment targets, making it possible to publish multiple WordPress sites from one coordinator while using separate AWS accounts and roles.

What’s new

• Added an optional AWS profile setting to the base deployment target.
• Added independent AWS profile selection to subscription-backed deployment profiles.
• Named profiles can be used for local S3 uploads and CloudFront invalidations without storing AWS access keys in WordPress.
• Temporary credentials attached to an individual queued job continue to take precedence over configured profile names.
• Added strict profile-name validation across WordPress, Publisher Core, and the exporter.
• Documented the separation between coordinator-side AWS profiles and CDK-allowlisted Lambda deployment roles.
• Added support for target-specific cross-account roles and external IDs.

Updated components

• Publisher Core 1.1.11
• Publisher Admin 1.0.13
• Static Publisher Exporter 1.1.81 or newer

Upgrade notes

Install the compatible exporter on the coordinator and restart the external queue runner.

For delegated cross-account deployment, update the Lambda worker stack with the target account’s S3-only deployment role and external ID, then reinstall the generated remote-workers.json.

The AWS profile configured in WordPress must exist for the operating-system user running the exporter. WordPress stores only the profile name, never its credentials.

Exporter 1.1.82 is recommended once available because it also contains the latest cross-account S3 streaming, relative URL rewriting, and rendered runtime-DOM fixes.

Static Publisher 1.0.25 – Site-wide change detection and safe page-cache purging

Highlights

Static Publisher 1.0.25 adds configurable site-wide change detection and a safe, cache-provider-independent page-cache purge workflow.

These additions allow incremental publishing to detect changes outside normal WordPress posts and pages, while ensuring delegated crawls do not accidentally export stale cached HTML.

Site-wide change detection

• Add configurable WordPress option dependencies to the global change-token signature.
• Add configurable, stable WordPress action hooks that invalidate all page tokens when site-wide content changes.
• Add a guarded manual action for invalidating all page change tokens.
• Hash watched option values and custom dependency payloads inside WordPress.
• Never expose raw watched option values through the token API or crawl logs.
• Reject frequently executed request-lifecycle hooks that could continuously invalidate incremental exports.
• Document how site-specific systems such as Code Snippets, global theme CSS, and other configuration providers can participate without adding vendor-specific logic to Static Publisher.

Page-cache integration

• Add an authenticated endpoint for purging the source site's page cache before crawl discovery.
• Keep Static Publisher independent of WP Super Cache, Cache Enabler, Redis, hosting-provider caches, and other concrete cache implementations.
• Introduce the versioned smartcloud_static_publisher_purge_page_cache_v1 provider contract for server-side adapters.
• Require a configured provider to explicitly confirm a complete purge.
• Stop the crawl before changing export output if cache purging is enabled but unavailable or unsuccessful.
• Leave existing installations unchanged when page-cache purging is disabled.
• Do not pre-warm the cache: the crawl naturally repopulates pages as they are requested.

Administration and documentation

• Add admin controls for watched WordPress options and action hooks.
• Add a dedicated “Purge page cache before crawl” setting.
• Add a confirmation-protected manual all-page invalidation action.
• Extend the documentation sidebar and developer guide with dependency, privacy, adapter, job-coverage, and cache-miss guidance.

Requirements

Page-cache purging requires @smart-cloud/publisher-exporter 1.1.74 or newer on the external queue runner.

A compatible server-side adapter must implement the generic purge-provider contract before the purge setting is enabled. Static Publisher does not bundle or require a specific page-cache plugin.

No exporter upgrade is required while page-cache purging remains disabled.

Upgrade notes

1. Install @smart-cloud/publisher-exporter 1.1.74 and restart the external queue runner.
2. Install and verify a compatible page-cache adapter.
3. Confirm that anonymous source requests produce a valid cache MISS-to-HIT sequence without caching authentication redirects or logged-in HTML.
4. Enable “Purge page cache before crawl” only after that verification.

The first incremental crawl after upgrading may render all supported pages once because the global token schema now includes the site revision and configured dependency hashes.

Static Publisher v1.0.24 – Lambda batching and reliable progress

Summary

Static Publisher 1.0.24 improves delegated publishing with configurable Lambda
batches, live progress reporting, corrected output metadata, and clearer processing
controls. The companion exporter updates also improve Chromium lifecycle handling
and saved-page accounting.

Lambda batching and browser lifecycle

• Render several URLs sequentially in one Lambda invocation while keeping the
  requested worker concurrency bounded.
• Use an isolated browser context for each page and release browser resources and
  temporary files after each batch.
• Retry failed URLs without repeating successful pages from the same batch.
• Configure render, rewrite, and deploy batch sizes from the administration screen.
• Report intra-batch worker progress through DynamoDB while work is still running.

Output metadata and progress accuracy

• Prefer the origin response Content-Type and use an extension-based fallback only
  when the response does not provide a usable type.
• Preserve content types through remote rewriting and repair mismatched target
  metadata during deployment.
• Count successful S3 workspace saves and retained outputs once per output path.
• Do not count failed requests or unrelated skips as saved pages.

Processing controls

• Put Processing concurrency in its own row, independent of Lambda delegation.
• Make Lambda-dependent settings available only when delegation is enabled.
• Align paired input fields and improve spacing below their descriptions.
• Allow numeric controls to remain temporarily empty while editing and provide
  increment/decrement controls.

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.

Static Publisher v1.0.22 – Governed job scheduling and status

• Bundles WP Suite Hub 2.5.16 so translation-catalog changes enqueue the matching static content refresh.
• Adds Professional and Agency content-sync scheduling to the Jobs screen with explicit deployment-target and enabled-rule selection.
• Adds the smartcloud-static-publisher/schedule-job Ability together with Publisher-governed target and content-sync rule discovery tools.
• Returns the actual job_id after scheduling and adds smartcloud-static-publisher/get-job-status for queue position, running state, completion time, and bounded redacted failure details.
• Requires Publisher authorization for publish and content-sync operations in protected Composer modes; Contributors may continue to schedule crawl and deploy work.
• Requires an exact active, baseline-ready rule and target pair and rejects missing, mismatched, or duplicate rule identities.
• Requires @smart-cloud/publisher-exporter 1.1.63 for the safe target/rule discovery snapshot and manual content-sync scheduling.

Install @smart-cloud/publisher-exporter 1.1.63 and restart the external queue runner. Then restart MCP or refresh Agent Composer tool discovery. Complete one successful normal publish before scheduling standard content-sync work so the selected rule and target pair has a ready baseline.

Static Publisher v1.0.21 – Delegated workers and targeted resources

• Added privacy-minimal cookie observation artifacts that authenticated exporter jobs can submit to installed Consent providers for manual classification.
• Added targeted render and tombstone operations for plugin-owned public resources, including Content Relations JSON projections.
• Added optional Lambda delegation for page rendering, text rewriting, and S3 deployment through independently configurable workers.
• Added live phase progress and separate staging, target-copy, and deletion reporting in the WordPress administration interface.
• Added durable remote-batch checkpoints and per-object deployment diagnostics to the local exporter log.
• Added a CDK-generated remote-workers.json runtime contract with allowlisted deployment targets and no host-specific path stored in WordPress.
• Hardened remote rendering against SSRF and VPC pivoting by validating documents, subresources, redirects, DNS answers, and IPv4/IPv6 destinations and by blocking service workers and WebSockets.
• Requires @smart-cloud/publisher-exporter 1.1.62 on every runner host.

Static Publisher v1.0.20 – Verified release coordination

• Added a versioned, read-only content journal and verified release contract for optional downstream consumers such as AI Kit.
• Publisher Exporter 1.1.54 now reports the exact active content-sync rule and target consumers using an atomic runtime snapshot.
• Historical, removed, stale, or ambiguous targets cannot authorize downstream Knowledge Base delivery.
• Existing crawling, deployment, invalidation, and content-sync behavior remains unchanged.