For the full list of changes, check out the Webiny 6.4.4external link release on GitHub.

Infrastructure
anchor

Custom Production Environments Are Now Recognized During Deployment (#5371external link)
anchor

Marking an environment as a production environment via the Infra.ProductionEnvironments setting in webiny.config.tsx previously had no effect — only the built-in prod and production names were treated as production, so custom environments (like stage) never received production-grade infrastructure such as a VPC. Configured production environments are now correctly recognized and deployed with the appropriate production setup.

If an environment was already deployed before being marked as production, the next deploy will create the VPC, move existing Lambdas into it, add VPC endpoints, and enable resource protection. This is a disruptive infrastructure migration that may replace resources and cause downtime. Review pulumi preview carefully and deploy during a maintenance window.