There was a bug in XP that made that event-lib return event data serialized in the wrong format.
What should have been a JSON object was instead a string that looked almost like JSON, but it was not.

The issue has been fixed in this release and the events are now properly formatted as JSON.
But some 3rd party applications and libraries that tried to work around the issue, by parsing the string, might break now.
If you are using event-lib, we recommend to test and verify that everything still works as expected.

This is an example of how the event was serialized in previous versions. The data is from a node event:

As of 6.13, content values in x-data, page-, and component-configs are now indexed “by type”, meaning that string-values are automatically fulltext indexed.
Also, html-areas in these configs are now properly stripped for html-tags when indexed as fulltext / n-gram.

Content created with earlier versions of XP does not have the same index settings.
Since the index-configuration of a content is stored within each content version,
each content must be updated (edit and save) to make the new index-values available.

This change is only relevant for particular cluster deployments of XP, where multiple nodes are running within the same server (OS/VM).

We have seen incidents where multiple XP instances have been started on the same machine, by accident creating a cluster.
To prevent this, the default cluster settings have been changed to use a specified port rather than a port range.

The cluster settings are available in the config-file: com.enonic.xp.elasticsearch.cfg

As if 6.13, if you still want to run more than one instance on the same machine, the setting transport.tcp.port must be set to a port range, e.g 9300-9302