Webiny 5.39.7 Changelog

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

Headless CMS

Unpublishing Content Entries - Ensuring All Internal Records Are Correctly Updated (#4137)

We’ve detected an issue where, upon unpublishing a content entry, an internal record was not correctly updated. This issue has now been resolved, and the internal records are now correctly updated when unpublishing content entries.

Brought BackpublishedOnandownedByEntry Meta Fields (GraphQL Schema Level) (#4156)

With the 5.39.0 release, we’ve removed the following two content entry meta fields:

1. publishedOn
2. ownedBy

These fields were removed because they were replaced with the new meta fields.

However, based on the user feedback, we’ve realized keeping these fields at least on the GraphQL schema level is important, as some users are still using them in their applications.

So, we’ve decided to bring back these fields to the GraphQL schema. They are marked as deprecated, and we recommend using the new meta fields instead. In the future, these fields will be removed from the GraphQL schema.

Made New Meta Fields Nullable (GraphQL Schema Level) (#4156)

On top of bringing back the publishedOn and ownedBy fields, we’ve also changed the new non-nullable entry meta fields and make them nullable.

This change was made to ensure a better experience while performing the 5.39.x data migration. Without this change, while the data migration is being performed, in most cases users with large data sets would be unable to use Headless CMS in the Admin app.

Page Builder

Website Settings Form - Fixed an Issue Related to Locale Switching (#4157)

In case a user switched to a different locale, submitting Page Builder’s Website settings form would result in an error. This issue has now been resolved, and the Website settings form now works as expected, regardless of the locale being used.

Data Migrations

Further Improving the 5.39.6-001 Data Migration (#4154)

We had to again revisit the 5.39.6-001 data migration. This is because the migration was taking too long to complete when large data sets were involved. We’ve now optimized the migration process, and it should now be much faster than before, in some cases up to 10 times faster.

Note that the improved data migration is not automatically executed, and that, by default, the migration will still be executed as it was before. If you want to execute the optimized migration, please take a look at the linked pull request for more information.

Introducing theWEBINY_MIGRATION_LOG_STREAMINGEnvironment Variable (#4136#4139)

Upon deploying the API project application, users can now use the WEBINY_MIGRATION_LOG_STREAMING environment variable in order to decide whether they want the data migration-related logs to be streamed into the terminal or not, during the deployment process.

Note that, since the streaming of data migration logs is enabled by default, the WEBINY_MIGRATION_LOG_STREAMING variable is essentially only used when the user wants to disable the streaming of data migration logs.

To disable the streaming of data migration logs, set the WEBINY_MIGRATION_LOG_STREAMING environment variable to false: