TAGR 4.10.0 HOW TO
TAGR 4.10.0 INSTALL
TAGR 4.10.0 UPDATE

We've recently updated our PHP support policy. Dropping support for PHP 7.1 and PHP 7.2 #

TAGR 4.10.0 HOW TO

We'll be providing guidance on how to transition to PHPUnit 9.5 closer to the release.

TAGR 4.10.0 UPDATE

If you want your own tests to run with PHP 8.0, then you have have to upgrade to PHPUnit 9.5 and update your tests to be compatible with the latest PHPUnit API. So your project's tests can still be run without modification. Silverstripe CMS Recipe 4.10.0 retains support for the sminnee/phpunit fork of PHPUnit 5.7. Read the Upgrading to PHPUnit 9.5 for PHP8 support guide for more details. All core module tests have been rewritten to run with PHPUnit 9.5. Adding support for PHPUnit 9.5 removed this road block. The major road block to official PHP 8.0 support was our reliance on a deprecated version of PHPUnit.

However, the Silverstripe CMS Recipe 4.10.0 is the first release to officially support PHP 8.0. Previous Silverstripe CMS Recipe releases could be run against PHP 8.0. PHPUnit 9.5 and PHP 8.0 official support # We didn't fully appreciate the nuances of composer's prefer-stable setting when we made this decision. We ended up tagging a few module as stable earlier than we normally would to get our CI green. In the process of getting all our modules compatible with PHPUnit 9.5, we had to force them to use silverstripe/framework 4.10 or greater. Run composer update -W to detect any unstable requirements. Once you are ready to upgrade to silverstripe/framework 4.10.0 stable then you'll need to remove that explicit constraint.Īlternatively, if you want to be 100% sure that you never run any unstable dependencies, you can set the minimum-stability in your composer file to stable. If you get conflicts, you might need to loosen some constraints to get older versions of some modules. To remedy this problem you can explicitly require 'silverstripe/framework': '~4.9.0' in your composer file and run composer update -W. If it comes out with 4.10.0-beta1 or 4.x-dev or 4.10-x-dev, you are running an unreleased version. This will show the currently installed version of silverstripe/framework. To double check what version of silverstripe/framework is installed on your project, run this command composer show silverstripe/framework.

TAGR 4.10.0 INSTALL

However, if you explicitly require the very latest version of a module that depends on silverstripe/framework ^4.10 then composer may install an unstable version of silverstripe/framework. For most projects, this won't be a problem if your composer.json file uses the 'prefer-stable': true flag. In the process of publishing Silverstripe CMS Recipe 4.10.0-beta1, we ended up releasing a few modules as 'stable' but with a requirement on the unstable silverstripe/framework 4.10. If you recently updated your project's composer.json file, you may have accidentally got an unstable version of silverstripe/framework.

Stable module forcing installation of unstable framework # Bringyourownideas/silverstripe-composer-update-checkerīringyourownideas/silverstripe-maintenanceĭnadesign/silverstripe-elemental-userforms

Tagr 4.10.0