Webiny 5.39.9 Changelog

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

Headless CMS

Published Records Updated Correctly Upon CallingcreateRevisionFrom(#4184)

Prior to this release, when immediately publishing a revision created using the createRevisionFrom method, the revision’s internal “published” record would not be updated correctly. This would cause the old published revisions to still be returned when performing queries.

This issue has been fixed, and now the published record is updated correctly when calling the createRevisionFrom method.

Added Model ID and Used Index Name When Logging Ignored ES Response Errors (#4186)

We’ve improved the logging of ignored ElasticSearch response errors by adding the model ID and the index name to the log message. This will make it easier to identify which model and index the error is related to.

Note that the errors we’re referring to here are errors that are, in most cases, not critical to the operation of the system, which is the reason they are ignored in the first place. These errors are ignored because they are usually related to the fact that a record is not yet indexed, which is expected behavior in some cases.

Data Migrations

Improved Disablement and Restoration of ElasticSearch Indexing Settings (#4187)

With this release, we’ve made a couple of improvements to the way ElasticSearch indexing settings are disabled and restored during data migrations. To provide context, when a data migration is run, we disable indexing on the index, perform the migration, and then restore the original settings. This is done to prevent indexing operations from happening during the migration, which speeds up the process and reduces the load on the database.

The changes are as follows.

First of all, when disabling indexing on an index, we no longer set the number_of_replicas setting to zero. Instead, we now do not touch this setting at all. This is because setting it to zero can cause data loss in case a shard is lost, as explained here, and also here.

Secondly, we’ve addressed an index settings restoration issue, which would happen if a user manually stopped a data migration and then reran it. More specifically, if a migration was stopped manually and then rerun, the restoration step would incorrectly again set the “disable indexing” settings. This is because it would use the index settings that were retrieved at the beginning of the new run, which, because the previous run has been manually stopped, still contain refresh_interval: -1. Ultimately, this setting would be applied when restoring index settings, effectively leaving the “indexing: disabled” setting still active.

5.39.6-001 Data Migration - Added Support forWEBINY_MIGRATION_FORCE_EXECUTE_5_39_6_001Environment Variable (#4188)

With this release, we’ve added the ability to force the execution of the improved 5.39.6-001 data migration by setting the WEBINY_MIGRATION_FORCE_EXECUTE_5_39_6_001 environment variable to true. This can be useful in cases where the migration has already been run, but you want to rerun it.

Note that this was already possible with all of the other data migrations, but the improved 5.39.6-001 data migration, that we released with the 5.39.6 release, did not support this feature. This has been fixed with this release.