Software update: Drupal 8.3.0

Version 8.3.0 of Drupal has been released, an update that should fix some security vulnerabilities. Drupal is a PHP-written, user-friendly and powerful content management platform, with which, for example, websites can be created. New in version 8.2 is, among other things, that blocks for text or media can be placed on pages without having to go to another administration page first. Furthermore, support for time periods has been added, where previously only a specific time could be used. The release notes for this release are as follows:

release notes

This is a minor version (feature release) of Drupal 8 and is ready for use on production sites. see the CHANGELOG.txt for a summary of changes and improvements since the last minor release. Learn more about Drupal 8 and the Drupal 8 release cycle.

If you encounter errors when updating to this release, see the known issues listed below. if you use rush, update to Drush 8.1.10 prior to using it to update Drupal. There are known issues updating to Drupal 8.3.0 using older versions of Drush.

This minor release provides new improvements and functionality without breaking backward compatibility (BC) for public APIs except where noted below. Note that there may be changes in internal APIs and experimental modules that require updates to contributed and custom modules and themes per Drupal core’s backwards compatibility and experimental module policies.

see the Drupal core change records for additional information on API changes. Translators should take note of a handful of minor string changes since the last release.

Backwards compatibility break to correct Serialization module output

#2751325: All serialized values ​​are strings, should be integers/booleans when appropriate corrects a bug that would output all scalar values ​​as strings rather than the correct data type in serialized output, including REST responses. This fix may require some client application updates if the application relies on these values ​​being strings.

An opt-in backwards compatibility mode is configurable at the site level, but not enabled by default. Read the change record for more information on this change and on configuring the backwards compatibility mode.