@smart-cloud/publisher-exporter 1.1.79 → 1.1.81

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
@@ -6,6 +6,23 @@ It is designed to run outside WordPress. The WordPress plugin only manages runti
6
6
 
7
7
  ## Release notes
8
8
 
9
+ ### 1.1.81
10
+
11
+ - Let the base deployment target and each named deployment profile select an optional AWS shared-config profile for local S3 deployment and CloudFront invalidation. One-time credentials attached to a queued job still take precedence, and only the profile name is stored in Publisher configuration.
12
+ - Let `remote-workers.json` independently select a host AWS profile when the coordinator must reach a worker stack through a named identity. This worker-plane profile is separate from the active deployment target profile.
13
+ - Allow an explicitly allowlisted delegated deploy target to assume a target-account role with an optional external ID. The worker reads the source workspace with its execution role and streams the object to S3 with target-role credentials, so neither identity needs access to both buckets.
14
+ - Validate profile names, target role ARNs, and external IDs before creating AWS clients, while keeping target role details out of generated site runtime configuration.
15
+
16
+ Upgrade the external coordinator, redeploy the Lambda worker stack with the cross-account target allowlist, and reinstall its generated `remote-workers.json` before selecting that target. Sites using only same-account ambient credentials retain their existing behavior.
17
+
18
+ ### 1.1.80
19
+
20
+ - Remove client-created top-level provider, portal, and overlay roots before serializing rendered HTML, including roots mounted through a bundled direct `react-dom/client` import that is not observable through `window.ReactDOM`.
21
+ - Ensure published pages run their parser-authored bootstrap and create fresh client providers instead of mistaking serialized, listener-free DOM for a live mount.
22
+ - Add a real headless Chromium regression test that reproduces the provider marker, captures the page, reloads the serialized HTML, and verifies successful provider reinitialization.
23
+
24
+ Upgrade both the external coordinator and delegated render-worker image to `1.1.80`, then rerender affected HTML pages. This is an exporter-only fix; no WordPress plugin update is required.
25
+
9
26
  ### 1.1.79
10
27
 
11
28
  - Let targeted content-sync trust pages already recorded in the verified baseline manifest even when the prior local render workspace has been cleaned up after a successful publish.
@@ -252,6 +269,21 @@ Archived files are gzip-compressed per file and listed in `job.json`. WordPress
252
269
 
253
270
  Prune old archive directories with `publisher-exporter prune-logs --runtime-dir /srv/site/runtime --older-than-days 30`. Add that command to daily cron or another retention scheduler that matches your log policy.
254
271
 
272
+ ## AWS credential profiles
273
+
274
+ The base deployment target and each named deployment target may set an optional
275
+ `awsProfile`. Local S3 deploy and CloudFront invalidation resolve that profile
276
+ from the queue-runner user's standard AWS shared config. Store only the profile
277
+ name in publisher configuration; never store access keys there. Explicit
278
+ temporary credentials attached to a queued job take precedence over the named
279
+ profile.
280
+
281
+ This setting is deliberately host-local. A delegated Lambda deploy cannot read
282
+ the WordPress VM's AWS profiles. Its CDK target uses either the deploy worker
283
+ execution role or an allowlisted cross-account target role. CloudFront
284
+ invalidation still runs on the coordinator and therefore uses the selected
285
+ host profile when one is configured.
286
+
255
287
  ## Optional Lambda workers
256
288
 
257
289
  The exporter includes protocol-v1 building blocks for delegating bounded
@@ -266,6 +298,12 @@ Its deploy script emits a `remote-workers.json` containing the
266
298
  versioned Lambda alias ARNs, workspace bucket/prefix, region, and generated
267
299
  assumable role. The file contains no static AWS access keys.
268
300
 
301
+ When the worker stack itself is reached through a host named profile, the file
302
+ may also contain `awsProfile`. That profile selects credentials for Lambda,
303
+ workspace S3, and progress DynamoDB access and is independent of the deployment
304
+ target profile. Without it, the exporter assumes the generated `roleArn` from
305
+ ambient credentials as before.
306
+
269
307
  Install that output with owner-only permissions at
270
308
  `<site-runtime>/remote-workers.json`, then validate the role, aliases, and
271
309
  function runtimes: