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..46261baff
--- /dev/null
+++ b/docs/release-notes/6.4.3/changelog.mdx
@@ -0,0 +1,28 @@
+---
+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.
+
+## 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.
+
+## 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
new file mode 100644
index 000000000..7dfb8bd19
--- /dev/null
+++ b/docs/release-notes/6.4.3/upgrade-guide.mdx
@@ -0,0 +1,61 @@
+---
+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.
+---
+
+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}
+```
+
+