Webiny 5.42.1 Changelog

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

Headless CMS

Consolidation of Headless CMS Backend Plugin Naming (#4502)

We noticed there were some naming-related inconsistencies in Headless CMS backend plugins. For example, when defining a new content model, users would use the createCmsModelPlugin factory function. On the other hand, when defining a single entry model, they would use the createSingleEntryModel factory function.

This PR not only consolidates the naming of these plugins but also exports them all via the @webiny/api-serverless-cms package. This way, users can import all CMS-related plugins from a single package.

Security

Improving the Headless CMS Permissions UI/UX (#4517)

A couple of UI improvements have been made to the Headless CMS permissions section. Most importantly, the three sections: Content Model Groups, Content Models, and Content Entries, are now always expanded and visible.

Headless CMS Security Permissions UI

(click to enlarge)

Previously, these sections would sometimes be shown and hidden in an unpredictable manner, which made it difficult to manage permissions.

configureAdminCognitoFederation- Use Name Instead of Type Where Needed (#4506,#4541)

Prior to this release, when setting up Amazon Cognito Federation and, more specifically, modifying the AWS cloud infrastructure, specifying the name property upon defining an OIDC provider would cause a deployment error:

This has now been resolved. Users can now specify the name property when defining an OIDC provider, and the deployment will complete successfully.

Cognito Federation - Ensure Admin User Entry Creation (#4534,#4540,#4551)

When using external identity providers, like Okta or Auth0, Webiny creates internal Admin User entries in the database upon successful login events. These entries can later be used for different purposes. For example, this enables Webiny to list all users when assigning folder level permissions.

With this release, we’ve fixed an issue where these Admin User entries were not being created when using external IdPs via Cognito Federation.

Deployments

Fixed VPC Configuration for Production Deployment (#4521)

In case you missed it, Webiny can be deployed into two deployment modes: development and production. As the names suggest, the development mode is used for development and testing purposes, while the production mode is used for live applications.

When comparing the two, the main difference is the usage of Amazon VPC (Virtual Private Cloud). In production mode, eligible cloud resources are deployed within a VPC, which provides an additional layer of security and isolation.

With this release, we’ve fixed an issue where the VPC configuration would not get applied when deploying in production mode, which is certainly not ideal.

Note that this issue would only occur when using the /enterprise version of Core, API, and Website project applications, within respective webiny.application.ts files:

When not using the /enterprise version, the VPC configuration would be applied correctly.

Refreshing the CI/CD Scaffold (#4526)

We’ve refreshed the GitHub Actions CI/CD scaffold to ensure it’s up-to-date with the latest changes. One of the main changes is the update of Node.js version that was used to run the CI/CD pipeline. The version has been updated from 14 all the way to 20.

Other

Feature-Based Architecture forapp-aco(#4513)

The @webiny/app-aco package now follows a feature-based architecture, improving modularity, maintainability, and scalability. The centralized useFolders hook has been replaced with dedicated hooks like useCreateFolder(), making the API more explicit and predictable.

• Better Maintainability – Features are modular and easier to update.
• Improved Scalability – New features can be added without affecting existing ones.
• Enhanced Developer Experience – More focused hooks improve readability and usability.

The useFolders hook is deprecated and will be removed in a future release. Update your code as follows:

Before (Deprecated)

After (New Approach)

Improved Report Dialog for Bulk Actions (#4550)

In this release, we have enhanced the report dialog displayed after executing bulk actions. Previously, messages in the dialog were truncated when they exceeded the available space, making it difficult for users to view the full details of the operation.

This enhancement improves the user experience by providing clearer feedback on bulk actions.