Valet-plus: Poll: Deprecate PHP 5.6

[Neodork]

What is the problem?
PHP 5.6 has been end of life for a while now. This created non-BC issues on the application and PHP (brew formula) side.

What was supposed to happen?
We want to deprecate PHP 5.6 from Valet+. But we would also like to get feedback from the Valet+ community to measure usage.

How often do you switch to PHP 5.6?

[ChristopherDosin]

I switched to 5.6 today because i needed it to migrate an old project.

Now i can't switch back to 7.1 - Any idea how to solve this issue?

valet use 7.1   
PHP Parse error:  syntax error, unexpected ':', expecting '{' in /Users/christopherdosin/.composer/vendor/symfony/deprecation-contracts/function.php on line 23

EDIT
Fixed with a composer global update

[zcuric]

I say deprecate all EOL PHP versions.

[joomkit]

I still want it for the odd legacy project waiting for funding before upgrade -but yeah it should go really

[phlbnks]

I'm keen to see it go - like @zcuric I think mapping to PHP lifespans makes sense and keeps it predictable.

[GrimLink]

Yes please!

[joostvanveen]

+1 for keeping 5.6 as long as possible. In theory, it is wise to ditch support for EOL versions. In practise, a lot of us have legacy projects to look after.