RFC: Drop PHP 7.3-support in all future Flow versions

aberl · December 21, 2022, 10:41am

We did raise minimum PHP version to 8 in Flow 8, no? So I think we did do something

neos/flow-development-collection/blob/8.0/Neos.Flow/composer.json#L9


      
          {
              "name": "neos/flow",
              "type": "neos-framework",
              "description": "Flow Application Framework",
              "homepage": "http://flow.neos.io",
              "license": ["MIT"],
          
              "require": {
                  "php": "^8.0",
          
                  "ext-zlib": "*",
                  "ext-SPL": "*",
                  "ext-json": "*",
                  "ext-reflection": "*",
                  "ext-xml": "*",
          
                  "neos/cache": "~8.0.0",
                  "neos/eel": "~8.0.0",
                  "neos/error-messages": "~8.0.0",

Regarding the “^8.0” and this somehow implicitly demanding us to add newer 8.x PHP versions to the build pipeline, I think we should consider to avoid doing “^” version matches, at least for PHP. But that’s a bit of a different topic that would need to be discussed separately. There are valid reasons for and against.

Personally think that we should be a little more aggressive with adding strict types to flow where we can.

Absolutely. The “where we can” is the hard part though There’s lots of hidden breakiness involved (see my efforts back in time), but I’m all for being agressive in the next major release if someone is up to the task of doing this (hint: psalm has some support for adding this automatically, but ofc needs some vetting)