Webiny 5.43.0 Changelog

For the full list of changes, check out the Webiny 5.43.0 release on GitHub.

Breaking Changes❗

Amazon OpenSearch Service - VPC Configuration Issue (#4532)

Prior to this release, when deploying a Webiny project with the existing Amazon VPC configuration in place, the Amazon OpenSearch service that Webiny deploys would not get correctly attached to the specified Amazon VPC (related subnets and security groups).

Because of the fact that, with this release, the VPC configuration now gets correctly attached to the Amazon OpenSearch cluster, redeploying an existing Webiny instance will cause the cluster to be DESTROYED AND RECREATED️, which means all data in the existing cluster will be lost❗

Luckily, the data can be recreated via the Elasticsearch Reindexing Task, which is something we cover in more detail in the 5.43.0 migration guide guide.

Headless CMS

FLP - Improved Permissions Inheritance (#4630)

✍️

Use Heartbeat in Record Locking Mechanism (#4583)

We refactored the record locking mechanism to use the heartbeat instead of React useEffect to unlock the record. Record is unlocked by default after 30 seconds of the system not receiving a heartbeat signal.

Deployments

Amazon OpenSearch Service - VPC Configuration Issue (#4532)

Prior to this release, when deploying a Webiny project with the existing Amazon VPC configuration in place, the Amazon OpenSearch service that Webiny deploys would not get correctly attached to the specified Amazon VPC (related subnets and security groups).

For example, the following configuration would not work as expected. Contrary to the expectation, the deployed Amazon OpenSearch cluster would not be attached to the specified OPENSEARCH_PRIVATE_SUBNETS subnets and OPENSEARCH_SECURITY_GROUPS security groups:

With this release, the underlying issue should no longer occur, and the above configuration will work as expected—with one minor change: instead of using elasticSearchDomainVpcConfig, users should now use opensearchDomainVpcConfig.

For more information on this change and also how to upgrade your existing Webiny project, please refer to the 5.43.0 migration guide guide.

Breaking Change❗

Because of the fact that, with this fix in place, the VPC configuration now gets correctly attached to the Amazon OpenSearch cluster, redeploying an existing Webiny instance will cause the cluster to be DESTROYED AND RECREATED️, which means all data in the existing cluster will be lost❗

Luckily, the data can be recreated via the Elasticsearch Reindexing Task.

For more information on how to migrate your existing Webiny project to the new VPC configuration and also how to safely reindex your data, please refer to the 5.43.0 migration guide guide.

Introducing thewebiny refreshCommand (#4552)

Multiple times in the past, we’ve seen users needing to run the pulumi refresh command in order to refresh the state of their Pulumi stacks.

Up until now, to do this, users had to run the following command:

To make this process a bit more straightforward, instead of the above command, users can now simply run:

Functionally, both commands do the same thing, but the new one is shorter and easier to remember.

Development

TypeScript 5.3.3 (#4464)

We have upgraded TypeScript to version 5.3.3. At this point we cannot go any higher because of the @rmwc/* packages.

Also, fastify was updated to 4.29.0 - which might affect users which are hooking into the fastify handler. If something is wrong in your code, the TypeScript build will break, and it is an easy fix - just check the fastify docs.

Webiny Packages Versions (#4628)

From now on, each time you run the Webiny CLI, it will check if all @webiny/* NPM packages in your project are using the same version. This is important because Webiny packages are tightly integrated, and having different versions can lead to unexpected issues.

The following screenshot shows an example of the CLI warning you about a version mismatch:

Webiny package versions check

(click to enlarge)