From c5d75f7317469688ad02860b6699538bc5b4fa75 Mon Sep 17 00:00:00 2001 From: webiny-bot Date: Thu, 11 Jun 2026 07:03:20 +0000 Subject: [PATCH 01/12] chore: generate changelog for 6.4.3 --- docs/release-notes/6.4.3/upgrade-guide.mdx | 61 ++++++++++++++++++++++ 1 file changed, 61 insertions(+) create mode 100644 docs/release-notes/6.4.3/upgrade-guide.mdx diff --git a/docs/release-notes/6.4.3/upgrade-guide.mdx b/docs/release-notes/6.4.3/upgrade-guide.mdx new file mode 100644 index 000000000..14f1fd727 --- /dev/null +++ b/docs/release-notes/6.4.3/upgrade-guide.mdx @@ -0,0 +1,61 @@ +--- +id: gi0if92q +title: Upgrade from 6.4.x to 6.4.3 +description: Learn how to upgrade Webiny from 6.4.x to 6.4.3. +--- + +import { Alert } from "@/components/Alert"; +import { AdditionalNotes } from "@/components/upgrade/AdditionalNotes"; + + + +- how to upgrade Webiny from 6.4.x to 6.4.3 + + + + + +Make sure to check out the [6.4.3 changelog](./changelog) to get familiar with the changes introduced in this release. + + + +## Step-by-Step Guide + +### 1. Upgrade Webiny Packages + +Upgrade all Webiny packages by running the following command: + +```bash +yarn webiny upgrade 6.4.3 --debug +``` + +Note that the command above will run upgrades for all available versions of Webiny up to 6.4.3. If there are upgrades for 6.4.1, 6.4.5, they will be ran. + +You can omit the version to upgrade to the latest available: + +```bash +yarn webiny upgrade --debug +``` + +Once the upgrade has finished, running the `yarn webiny --version` command in your terminal should return **6.4.3**. + + + +If the above command fails or is not available in your setup, you can run the upgrade script directly via `npx`: + +```bash +npx https://github.com/webiny/webiny-upgrades-v6 6.4.3 --debug +``` + + + +### 2. Deploy Your Project + +Proceed by redeploying your Webiny project: + +```bash +# Execute in your project root. +yarn webiny deploy --env {environment} +``` + + From 7f43f72abd44304bd9bff083a34af581b3bd3cc6 Mon Sep 17 00:00:00 2001 From: webiny-bot Date: Thu, 11 Jun 2026 08:09:45 +0000 Subject: [PATCH 02/12] chore: regenerate release notes for 6.4.3 --- docs/release-notes/6.4.3/changelog.ai.txt | 8 ++++++++ docs/release-notes/6.4.3/changelog.mdx | 16 ++++++++++++++++ docs/release-notes/6.4.3/upgrade-guide.mdx | 2 +- 3 files changed, 25 insertions(+), 1 deletion(-) create mode 100644 docs/release-notes/6.4.3/changelog.ai.txt create mode 100644 docs/release-notes/6.4.3/changelog.mdx diff --git a/docs/release-notes/6.4.3/changelog.ai.txt b/docs/release-notes/6.4.3/changelog.ai.txt new file mode 100644 index 000000000..4475840c8 --- /dev/null +++ b/docs/release-notes/6.4.3/changelog.ai.txt @@ -0,0 +1,8 @@ +AI Context: 6.4.3 Changelog (changelog.mdx) + +This file tracks manual edits made after the generation script ran. +The script reads the "Skipped PRs" section to avoid re-adding removed entries. + +## Skipped PRs + +## Manual Rewrites diff --git a/docs/release-notes/6.4.3/changelog.mdx b/docs/release-notes/6.4.3/changelog.mdx new file mode 100644 index 000000000..e87c2cb90 --- /dev/null +++ b/docs/release-notes/6.4.3/changelog.mdx @@ -0,0 +1,16 @@ +--- +id: anre1c68 +title: Webiny 6.4.3 Changelog +description: See what's new in Webiny version 6.4.3 +--- + +import { GithubRelease } from "@/components/GithubRelease"; +import { Alert } from "@/components/Alert"; + + + +## Headless CMS + +### Fixed Workflow State Dirty Detection and Review Flow ([#5283](https://github.com/webiny/webiny-js/pull/5283)) + +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. diff --git a/docs/release-notes/6.4.3/upgrade-guide.mdx b/docs/release-notes/6.4.3/upgrade-guide.mdx index 14f1fd727..8e4d3bb74 100644 --- a/docs/release-notes/6.4.3/upgrade-guide.mdx +++ b/docs/release-notes/6.4.3/upgrade-guide.mdx @@ -1,5 +1,5 @@ --- -id: gi0if92q +id: xzylv7u0 title: Upgrade from 6.4.x to 6.4.3 description: Learn how to upgrade Webiny from 6.4.x to 6.4.3. --- From 1dd38eba0830552b54426ff9cd230d8089be7320 Mon Sep 17 00:00:00 2001 From: webiny-bot Date: Thu, 11 Jun 2026 20:13:23 +0000 Subject: [PATCH 03/12] chore: regenerate release notes for 6.4.3 --- docs/release-notes/6.4.3/changelog.mdx | 6 ++++++ docs/release-notes/6.4.3/upgrade-guide.mdx | 2 +- 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/docs/release-notes/6.4.3/changelog.mdx b/docs/release-notes/6.4.3/changelog.mdx index e87c2cb90..5343571e6 100644 --- a/docs/release-notes/6.4.3/changelog.mdx +++ b/docs/release-notes/6.4.3/changelog.mdx @@ -14,3 +14,9 @@ import { Alert } from "@/components/Alert"; ### Fixed Workflow State Dirty Detection and Review Flow ([#5283](https://github.com/webiny/webiny-js/pull/5283)) 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. + +## Admin + +### Prevent Duplicate Team Selections in Workflow Steps ([#5286](https://github.com/webiny/webiny-js/pull/5286)) + +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. diff --git a/docs/release-notes/6.4.3/upgrade-guide.mdx b/docs/release-notes/6.4.3/upgrade-guide.mdx index 8e4d3bb74..220584b4a 100644 --- a/docs/release-notes/6.4.3/upgrade-guide.mdx +++ b/docs/release-notes/6.4.3/upgrade-guide.mdx @@ -1,5 +1,5 @@ --- -id: xzylv7u0 +id: ob3ozv8d title: Upgrade from 6.4.x to 6.4.3 description: Learn how to upgrade Webiny from 6.4.x to 6.4.3. --- From b84d35cccdf02463726780b36ab02ae427591cfc Mon Sep 17 00:00:00 2001 From: webiny-bot Date: Fri, 12 Jun 2026 08:14:47 +0000 Subject: [PATCH 04/12] chore: regenerate release notes for 6.4.3 --- docs/release-notes/6.4.3/changelog.mdx | 6 ++++++ docs/release-notes/6.4.3/upgrade-guide.mdx | 2 +- 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/docs/release-notes/6.4.3/changelog.mdx b/docs/release-notes/6.4.3/changelog.mdx index 5343571e6..46261baff 100644 --- a/docs/release-notes/6.4.3/changelog.mdx +++ b/docs/release-notes/6.4.3/changelog.mdx @@ -20,3 +20,9 @@ MobX observable proxies were being passed directly to `structuredClone` and `JSO ### Prevent Duplicate Team Selections in Workflow Steps ([#5286](https://github.com/webiny/webiny-js/pull/5286)) 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 + +### Fix Teams Selector Not Working in Workflow Step Form ([#5285](https://github.com/webiny/webiny-js/pull/5285)) + +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. diff --git a/docs/release-notes/6.4.3/upgrade-guide.mdx b/docs/release-notes/6.4.3/upgrade-guide.mdx index 220584b4a..eeee4a6e0 100644 --- a/docs/release-notes/6.4.3/upgrade-guide.mdx +++ b/docs/release-notes/6.4.3/upgrade-guide.mdx @@ -1,5 +1,5 @@ --- -id: ob3ozv8d +id: 9ns9skhr title: Upgrade from 6.4.x to 6.4.3 description: Learn how to upgrade Webiny from 6.4.x to 6.4.3. --- From 5a0e89e29ee0c9ed80110bd109c01ccab66f6461 Mon Sep 17 00:00:00 2001 From: webiny-bot Date: Fri, 12 Jun 2026 09:17:18 +0000 Subject: [PATCH 05/12] chore: regenerate release notes for 6.4.3 --- docs/release-notes/6.4.3/upgrade-guide.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/release-notes/6.4.3/upgrade-guide.mdx b/docs/release-notes/6.4.3/upgrade-guide.mdx index eeee4a6e0..7dfb8bd19 100644 --- a/docs/release-notes/6.4.3/upgrade-guide.mdx +++ b/docs/release-notes/6.4.3/upgrade-guide.mdx @@ -1,5 +1,5 @@ --- -id: 9ns9skhr +id: cdkeqiuf title: Upgrade from 6.4.x to 6.4.3 description: Learn how to upgrade Webiny from 6.4.x to 6.4.3. --- From 1ec9362cae0d84e30b5fbe9b2da9a52c6369f6dd Mon Sep 17 00:00:00 2001 From: webiny-bot Date: Thu, 18 Jun 2026 08:08:25 +0000 Subject: [PATCH 06/12] chore: regenerate release notes for 6.4.3 --- docs/release-notes/6.4.3/changelog.mdx | 36 ++++++++++++++++++++++ docs/release-notes/6.4.3/upgrade-guide.mdx | 2 +- 2 files changed, 37 insertions(+), 1 deletion(-) diff --git a/docs/release-notes/6.4.3/changelog.mdx b/docs/release-notes/6.4.3/changelog.mdx index 46261baff..91dbf9987 100644 --- a/docs/release-notes/6.4.3/changelog.mdx +++ b/docs/release-notes/6.4.3/changelog.mdx @@ -15,6 +15,10 @@ import { Alert } from "@/components/Alert"; 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 ([#5287](https://github.com/webiny/webiny-js/pull/5287)) + +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 ### Prevent Duplicate Team Selections in Workflow Steps ([#5286](https://github.com/webiny/webiny-js/pull/5286)) @@ -26,3 +30,35 @@ When configuring workflow steps, users could previously select the same team mul ### Fix Teams Selector Not Working in Workflow Step Form ([#5285](https://github.com/webiny/webiny-js/pull/5285)) 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 + +### Custom Domains via Dynamically Created Infrastructure ([#5298](https://github.com/webiny/webiny-js/pull/5298)) + +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: + +```typescript +import * as aws from "@pulumi/aws"; +import { ApiPulumi, SetApiCustomDomains } from "webiny/infra/api"; + +class ApiCustomDomain implements ApiPulumi.Interface { + constructor(private setCustomDomains: SetApiCustomDomains.Interface) {} + + execute(app: ApiPulumi.Params) { + const certificate = app.addResource(aws.acm.Certificate, { + name: "api-custom-domain-cert", + config: { domainName: "api.example.com", validationMethod: "DNS" } + }); + + this.setCustomDomains.execute({ + domains: ["api.example.com"], + acmCertificateArn: certificate.output.arn + }); + } +} + +export default ApiPulumi.createImplementation({ + implementation: ApiCustomDomain, + dependencies: [SetApiCustomDomains] +}); +``` diff --git a/docs/release-notes/6.4.3/upgrade-guide.mdx b/docs/release-notes/6.4.3/upgrade-guide.mdx index 7dfb8bd19..e76faad8d 100644 --- a/docs/release-notes/6.4.3/upgrade-guide.mdx +++ b/docs/release-notes/6.4.3/upgrade-guide.mdx @@ -1,5 +1,5 @@ --- -id: cdkeqiuf +id: 9u5uf3nh title: Upgrade from 6.4.x to 6.4.3 description: Learn how to upgrade Webiny from 6.4.x to 6.4.3. --- From 7ef2d0d9aa761c660f4fae6af3233a00380c8bb9 Mon Sep 17 00:00:00 2001 From: webiny-bot Date: Thu, 18 Jun 2026 11:05:11 +0000 Subject: [PATCH 07/12] chore: regenerate release notes for 6.4.3 --- docs/release-notes/6.4.3/changelog.mdx | 4 ++++ docs/release-notes/6.4.3/upgrade-guide.mdx | 2 +- 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/release-notes/6.4.3/changelog.mdx b/docs/release-notes/6.4.3/changelog.mdx index 91dbf9987..8d9d9a26e 100644 --- a/docs/release-notes/6.4.3/changelog.mdx +++ b/docs/release-notes/6.4.3/changelog.mdx @@ -25,6 +25,10 @@ Scheduled publish and unpublish actions created on non-root tenants would fail t 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. +### Consistent, Click-to-Edit Title in the Page and Content Model Editors ([#5306](https://github.com/webiny/webiny-js/pull/5306)) + +The title in the top-left of the Website Builder page editor and the Headless CMS content model editor previously looked and behaved differently. They now share the same appearance and behavior — orange text that highlights on hover and turns into an inline field when clicked — so renaming a page or a content model feels the same across both editors. + ## Workflows ### Fix Teams Selector Not Working in Workflow Step Form ([#5285](https://github.com/webiny/webiny-js/pull/5285)) diff --git a/docs/release-notes/6.4.3/upgrade-guide.mdx b/docs/release-notes/6.4.3/upgrade-guide.mdx index e76faad8d..c42f7899e 100644 --- a/docs/release-notes/6.4.3/upgrade-guide.mdx +++ b/docs/release-notes/6.4.3/upgrade-guide.mdx @@ -1,5 +1,5 @@ --- -id: 9u5uf3nh +id: xfle23hg title: Upgrade from 6.4.x to 6.4.3 description: Learn how to upgrade Webiny from 6.4.x to 6.4.3. --- From 92d9fda324996e619c890f9f795341d27aa23662 Mon Sep 17 00:00:00 2001 From: webiny-bot Date: Fri, 19 Jun 2026 13:12:53 +0000 Subject: [PATCH 08/12] chore: regenerate release notes for 6.4.3 --- docs/release-notes/6.4.3/upgrade-guide.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/release-notes/6.4.3/upgrade-guide.mdx b/docs/release-notes/6.4.3/upgrade-guide.mdx index c42f7899e..c947a4ba2 100644 --- a/docs/release-notes/6.4.3/upgrade-guide.mdx +++ b/docs/release-notes/6.4.3/upgrade-guide.mdx @@ -1,5 +1,5 @@ --- -id: xfle23hg +id: fa35j5hh title: Upgrade from 6.4.x to 6.4.3 description: Learn how to upgrade Webiny from 6.4.x to 6.4.3. --- From b7202b318a651aacec6035ab6a953244b01b22d5 Mon Sep 17 00:00:00 2001 From: webiny-bot Date: Fri, 19 Jun 2026 13:46:54 +0000 Subject: [PATCH 09/12] chore: regenerate release notes for 6.4.3 --- docs/release-notes/6.4.3/upgrade-guide.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/release-notes/6.4.3/upgrade-guide.mdx b/docs/release-notes/6.4.3/upgrade-guide.mdx index c947a4ba2..94458f5ab 100644 --- a/docs/release-notes/6.4.3/upgrade-guide.mdx +++ b/docs/release-notes/6.4.3/upgrade-guide.mdx @@ -1,5 +1,5 @@ --- -id: fa35j5hh +id: r1fk64qm title: Upgrade from 6.4.x to 6.4.3 description: Learn how to upgrade Webiny from 6.4.x to 6.4.3. --- From 4db38dd98c551cbae46c83a0b1cf577a93d0e5e3 Mon Sep 17 00:00:00 2001 From: webiny-bot Date: Tue, 23 Jun 2026 08:14:22 +0000 Subject: [PATCH 10/12] chore: regenerate release notes for 6.4.3 --- docs/release-notes/6.4.3/changelog.mdx | 4 ++++ docs/release-notes/6.4.3/upgrade-guide.mdx | 2 +- 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/release-notes/6.4.3/changelog.mdx b/docs/release-notes/6.4.3/changelog.mdx index 8d9d9a26e..ef6866877 100644 --- a/docs/release-notes/6.4.3/changelog.mdx +++ b/docs/release-notes/6.4.3/changelog.mdx @@ -19,6 +19,10 @@ MobX observable proxies were being passed directly to `structuredClone` and `JSO 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. +### Fixed Content Entry Patch Operations Failing in Certain Edge Cases ([#5317](https://github.com/webiny/webiny-js/pull/5317)) + +Patch operations on content entries could fail unexpectedly in certain edge cases. This has been fixed to ensure reliable updates when using the patch API. + ## Admin ### Prevent Duplicate Team Selections in Workflow Steps ([#5286](https://github.com/webiny/webiny-js/pull/5286)) diff --git a/docs/release-notes/6.4.3/upgrade-guide.mdx b/docs/release-notes/6.4.3/upgrade-guide.mdx index 94458f5ab..5fedc7ae9 100644 --- a/docs/release-notes/6.4.3/upgrade-guide.mdx +++ b/docs/release-notes/6.4.3/upgrade-guide.mdx @@ -1,5 +1,5 @@ --- -id: r1fk64qm +id: 0xa13n5w title: Upgrade from 6.4.x to 6.4.3 description: Learn how to upgrade Webiny from 6.4.x to 6.4.3. --- From b7fd6f85bff6f7f1ffdb8232152e1739a7e0457a Mon Sep 17 00:00:00 2001 From: webiny-bot Date: Tue, 23 Jun 2026 08:51:40 +0000 Subject: [PATCH 11/12] chore: regenerate release notes for 6.4.3 --- docs/release-notes/6.4.3/upgrade-guide.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/release-notes/6.4.3/upgrade-guide.mdx b/docs/release-notes/6.4.3/upgrade-guide.mdx index 5fedc7ae9..97fb5e300 100644 --- a/docs/release-notes/6.4.3/upgrade-guide.mdx +++ b/docs/release-notes/6.4.3/upgrade-guide.mdx @@ -1,5 +1,5 @@ --- -id: 0xa13n5w +id: eyavtfrs title: Upgrade from 6.4.x to 6.4.3 description: Learn how to upgrade Webiny from 6.4.x to 6.4.3. --- From 948268044c44b550f628121c8ab5a2c42eb68084 Mon Sep 17 00:00:00 2001 From: webiny-bot Date: Wed, 24 Jun 2026 10:41:13 +0000 Subject: [PATCH 12/12] chore: regenerate release notes for 6.4.3 --- docs/release-notes/6.4.3/changelog.mdx | 11 +++++++++++ docs/release-notes/6.4.3/upgrade-guide.mdx | 2 +- 2 files changed, 12 insertions(+), 1 deletion(-) diff --git a/docs/release-notes/6.4.3/changelog.mdx b/docs/release-notes/6.4.3/changelog.mdx index ef6866877..7ceb70a8d 100644 --- a/docs/release-notes/6.4.3/changelog.mdx +++ b/docs/release-notes/6.4.3/changelog.mdx @@ -70,3 +70,14 @@ export default ApiPulumi.createImplementation({ dependencies: [SetApiCustomDomains] }); ``` + +### Fixed Remote Pulumi Backend Detection for Custom Production Environments ([#5305](https://github.com/webiny/webiny-js/pull/5305)) + +Deploying to a custom production environment (e.g. `staging` registered via `Infra.ProductionEnvironments`) would fail with `Cannot deploy to production with local state files.` even when a remote Pulumi backend was correctly configured and state was being written to S3. + +Two issues caused this: + +- The production environment validation was hard-coded to only check `prod` and `production`, ignoring any custom environments you registered via `Infra.ProductionEnvironments`. +- The remote backend detection checked different environment variables (`WEBINY_CLI_PULUMI_BACKEND`) than what the Pulumi login service actually used (`WEBINY_PULUMI_BACKEND`), so it always concluded no remote backend was configured. + +Both services now use `WEBINY_CLI_PULUMI_BACKEND` as the canonical variable, with `WEBINY_PULUMI_BACKEND` supported as a legacy fallback for backwards compatibility. No changes to your existing CI/CD configuration are required. diff --git a/docs/release-notes/6.4.3/upgrade-guide.mdx b/docs/release-notes/6.4.3/upgrade-guide.mdx index 97fb5e300..7fbe03df3 100644 --- a/docs/release-notes/6.4.3/upgrade-guide.mdx +++ b/docs/release-notes/6.4.3/upgrade-guide.mdx @@ -1,5 +1,5 @@ --- -id: eyavtfrs +id: udhwo0dp title: Upgrade from 6.4.x to 6.4.3 description: Learn how to upgrade Webiny from 6.4.x to 6.4.3. ---