Skip to content

Commit 5f8050e

Browse files
github-actions[bot]webiny-bot
github-actions[bot]
and
webiny-bot
authored
feat: release 6.4.3 (#799)
Co-authored-by: webiny-bot <webiny-bot@webiny.com>
1 parent 3a72814 commit 5f8050e

3 files changed

Lines changed: 152 additions & 0 deletions

File tree

‎docs/release-notes/6.4.3/changelog.ai.txt‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
AI Context: 6.4.3 Changelog (changelog.mdx)
2+
3+
This file tracks manual edits made after the generation script ran.
4+
The script reads the "Skipped PRs" section to avoid re-adding removed entries.
5+
6+
## Skipped PRs
7+
8+
## Manual Rewrites

‎docs/release-notes/6.4.3/changelog.mdx‎

Lines changed: 83 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,83 @@
1+
---
2+
id: anre1c68
3+
title: Webiny 6.4.3 Changelog
4+
description: See what's new in Webiny version 6.4.3
5+
---
6+
7+
import { GithubRelease } from "@/components/GithubRelease";
8+
import { Alert } from "@/components/Alert";
9+
10+
<GithubRelease version={"6.4.3"} />
11+
12+
## Headless CMS
13+
14+
### Fixed Workflow State Dirty Detection and Review Flow ([#5283](https://github.com/webiny/webiny-js/pull/5283))
15+
16+
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.
17+
18+
### Fixed Scheduled Actions Failing on Non-Root Tenants ([#5287](https://github.com/webiny/webiny-js/pull/5287))
19+
20+
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.
21+
22+
### Fixed Content Entry Patch Operations Failing in Certain Edge Cases ([#5317](https://github.com/webiny/webiny-js/pull/5317))
23+
24+
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.
25+
26+
## Admin
27+
28+
### Prevent Duplicate Team Selections in Workflow Steps ([#5286](https://github.com/webiny/webiny-js/pull/5286))
29+
30+
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.
31+
32+
### Consistent, Click-to-Edit Title in the Page and Content Model Editors ([#5306](https://github.com/webiny/webiny-js/pull/5306))
33+
34+
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.
35+
36+
## Workflows
37+
38+
### Fix Teams Selector Not Working in Workflow Step Form ([#5285](https://github.com/webiny/webiny-js/pull/5285))
39+
40+
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.
41+
42+
## Infrastructure
43+
44+
### Custom Domains via Dynamically Created Infrastructure ([#5298](https://github.com/webiny/webiny-js/pull/5298))
45+
46+
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:
47+
48+
```typescript
49+
import * as aws from "@pulumi/aws";
50+
import { ApiPulumi, SetApiCustomDomains } from "webiny/infra/api";
51+
52+
class ApiCustomDomain implements ApiPulumi.Interface {
53+
constructor(private setCustomDomains: SetApiCustomDomains.Interface) {}
54+
55+
execute(app: ApiPulumi.Params) {
56+
const certificate = app.addResource(aws.acm.Certificate, {
57+
name: "api-custom-domain-cert",
58+
config: { domainName: "api.example.com", validationMethod: "DNS" }
59+
});
60+
61+
this.setCustomDomains.execute({
62+
domains: ["api.example.com"],
63+
acmCertificateArn: certificate.output.arn
64+
});
65+
}
66+
}
67+
68+
export default ApiPulumi.createImplementation({
69+
implementation: ApiCustomDomain,
70+
dependencies: [SetApiCustomDomains]
71+
});
72+
```
73+
74+
### Fixed Remote Pulumi Backend Detection for Custom Production Environments ([#5305](https://github.com/webiny/webiny-js/pull/5305))
75+
76+
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.
77+
78+
Two issues caused this:
79+
80+
- The production environment validation was hard-coded to only check `prod` and `production`, ignoring any custom environments you registered via `Infra.ProductionEnvironments`.
81+
- 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.
82+
83+
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.

‎docs/release-notes/6.4.3/upgrade-guide.mdx‎

Lines changed: 61 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,61 @@
1+
---
2+
id: udhwo0dp
3+
title: Upgrade from 6.4.x to 6.4.3
4+
description: Learn how to upgrade Webiny from 6.4.x to 6.4.3.
5+
---
6+
7+
import { Alert } from "@/components/Alert";
8+
import { AdditionalNotes } from "@/components/upgrade/AdditionalNotes";
9+
10+
<Alert type="success" title="What you'll learn">
11+
12+
- how to upgrade Webiny from 6.4.x to 6.4.3
13+
14+
</Alert>
15+
16+
<Alert type="info">
17+
18+
Make sure to check out the [6.4.3 changelog](./changelog) to get familiar with the changes introduced in this release.
19+
20+
</Alert>
21+
22+
## Step-by-Step Guide
23+
24+
### 1. Upgrade Webiny Packages
25+
26+
Upgrade all Webiny packages by running the following command:
27+
28+
```bash
29+
yarn webiny upgrade 6.4.3 --debug
30+
```
31+
32+
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.
33+
34+
You can omit the version to upgrade to the latest available:
35+
36+
```bash
37+
yarn webiny upgrade --debug
38+
```
39+
40+
Once the upgrade has finished, running the `yarn webiny --version` command in your terminal should return **6.4.3**.
41+
42+
<Alert type="info">
43+
44+
If the above command fails or is not available in your setup, you can run the upgrade script directly via `npx`:
45+
46+
```bash
47+
npx https://github.com/webiny/webiny-upgrades-v6 6.4.3 --debug
48+
```
49+
50+
</Alert>
51+
52+
### 2. Deploy Your Project
53+
54+
Proceed by redeploying your Webiny project:
55+
56+
```bash
57+
# Execute in your project root.
58+
yarn webiny deploy --env {environment}
59+
```
60+
61+
<AdditionalNotes />

0 commit comments

Comments
 (0)