Webiny Docs home page
For the full list of changes, check out the Webiny 6.4.3external link release on GitHub.

Headless CMS
anchor

Fixed Workflow State Dirty Detection and Review Flow (#5283external link)
anchor

MobX observable proxies were being passed directly to structuredClone and JSON.stringify in the workflow state management code, which could cause runtime errors or produce inconsistent snapshots. The WorkflowStateModel.toJS() method was also returning model class instances instead of plain data objects for step properties. These issues have been fixed — workflow state dirty detection, review flows (request review, approve, reject), and list pagination now work reliably.

Fixed Scheduled Actions Failing on Non-Root Tenants (#5287external link)
anchor

Scheduled publish and unpublish actions created on non-root tenants would fail to execute. The event handler ran in the root tenant context and couldn’t locate entries stored under the originating tenant. This has been fixed — scheduled actions now correctly track and execute within their original tenant context.

Admin
anchor

Prevent Duplicate Team Selections in Workflow Steps (#5286external link)
anchor

When configuring workflow steps, users could previously select the same team multiple times in the teams autocomplete field. The TeamsMultiAutocomplete component now enforces unique selections, preventing duplicate team entries.

Workflows
anchor

Fix Teams Selector Not Working in Workflow Step Form (#5285external link)
anchor

After a recent UI library migration, the teams selector in the workflow step form stopped working — selecting a team would still show a validation error, and previously saved teams were not shown as selected when editing. Both issues are now fixed.

Infrastructure
anchor

Custom Domains via Dynamically Created Infrastructure (#5298external link)
anchor

You can now point a custom domain at your Admin or API app and have Webiny provision the required SSL certificate during deployment, instead of creating and supplying one beforehand. Inject SetApiCustomDomains or SetAdminCustomDomains into your Pulumi implementation to create the certificate and attach the domain in a single deploy: