Release 6.4.11

docs/release-notes/6.4.11/changelog.ai.txt

@@ -0,0 +1,11 @@
+AI Context: 6.4.11 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
+
+- #5683 — Rewritten to lead with the user-facing impact (page search in the Website Builder came back) instead of the internal cause. Dropped the explanation of the query targeting the object field name rather than its nested leaf values, and the `values.<storageId>.*` detail. Heading changed from "Fixed Full-Text Search on `searchableJson` Fields for OpenSearch Deployments" to "Fixed Page Search and Search on Models With JSON Fields".
+- #5677 — Dropped the note about mobile visitors seeing a flash of the desktop layout. Replaced it with a statement that SSR-side grid column stacking needs more investigation and a proper fix will land in a future release.

docs/release-notes/6.4.11/changelog.mdx

@@ -0,0 +1,47 @@
+---
+id: cmk9w5cl
+title: Webiny 6.4.11 Changelog
+description: See what's new in Webiny version 6.4.11
+---
+
+import { GithubRelease } from "@/components/GithubRelease";
+import { Alert } from "@/components/Alert";
+
+<GithubRelease version={"6.4.11"} />
+
+## Headless CMS
+
+### Fixed Page Search and Search on Models With JSON Fields ([#5683](https://github.com/webiny/webiny-js/pull/5683))
+
+Searching for pages in the Website Builder returned nothing on DynamoDB + OpenSearch deployments, no matter what you typed. The same applied to any Headless CMS model with a `searchableJson` field, since page metadata is stored in one.
+
+Search now returns the results you would expect. DynamoDB-only deployments were never affected, so nothing changes there.
+
+## Infrastructure
+
+### Expose `minimumProtocolVersion` for Custom Domain CloudFront Distributions ([#5680](https://github.com/webiny/webiny-js/pull/5680))
+
+When configuring custom domains for Admin or API distributions, you can now set the CloudFront TLS security policy directly through the extension configuration. Previously, changing this required patching `@webiny/project-aws`.
+
+```typescript
+import { extensions } from "webiny/infra";
+
+extensions.addExtension({
+  type: "Infra/Admin/CustomDomains",
+  params: {
+    domains: ["admin.example.com"],
+    certificateArn: "arn:aws:acm:...",
+    minimumProtocolVersion: "TLSv1.2_2021"
+  }
+});
+```
+
+Supported values match the full CloudFront policy set: `SSLv3`, `TLSv1`, `TLSv1_2016`, `TLSv1.1_2016`, `TLSv1.2_2018`, `TLSv1.2_2019`, and `TLSv1.2_2021`. The parameter is optional and omitted from the CloudFront configuration when not set, so existing distributions see no change.
+
+## Website Builder
+
+### Fixed React Server Component Crash When Initializing the Content SDK ([#5677](https://github.com/webiny/webiny-js/pull/5677))
+
+Version 6.4.10 introduced a bug where initializing the Website Builder SDK from a React Server Component would throw `TypeError: viewportManager.setBreakpoints is not a function`. This happened because the viewport manager is a client-only module, and RSC receives a client reference instead of the actual function. The issue blocked page loading and redirect resolution entirely when using RSC.
+
+This release reverts the change that caused the crash. Grid column stacking returns to the 6.4.9 behaviour: it resolves on the client after hydration rather than during SSR. Resolving it during SSR needs more investigation, so we're taking the time to work out a proper fix and will ship it in a future release.

docs/release-notes/6.4.11/upgrade-guide.mdx

@@ -0,0 +1,61 @@
+---
+id: etx9jn4o
+title: Upgrade from 6.4.x to 6.4.11
+description: Learn how to upgrade Webiny from 6.4.x to 6.4.11.
+---
+
+import { Alert } from "@/components/Alert";
+import { AdditionalNotes } from "@/components/upgrade/AdditionalNotes";
+
+<Alert type="success" title="What you'll learn">
+
+- how to upgrade Webiny from 6.4.x to 6.4.11
+
+</Alert>
+
+<Alert type="info">
+
+Make sure to check out the [6.4.11 changelog](./changelog) to get familiar with the changes introduced in this release.
+
+</Alert>
+
+## Step-by-Step Guide
+
+### 1. Upgrade Webiny Packages
+
+Upgrade all Webiny packages by running the following command:
+
+```bash
+yarn webiny upgrade 6.4.11 --debug
+```
+
+Note that the command above will run upgrades for all available versions of Webiny up to 6.4.11. 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.11**.
+
+<Alert type="info">
+
+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.11 --debug
+```
+
+</Alert>
+
+### 2. Deploy Your Project
+
+Proceed by redeploying your Webiny project:
+
+```bash
+# Execute in your project root.
+yarn webiny deploy --env {environment}
+```
+
+<AdditionalNotes />