Skip to content

Drop support for PHP 8.2, and PHP 8.3#810

Open
lyrixx wants to merge 1 commit into
mainfrom
bump-php
Open

Drop support for PHP 8.2, and PHP 8.3#810
lyrixx wants to merge 1 commit into
mainfrom
bump-php

Conversation

@lyrixx
Copy link
Copy Markdown
Member

@lyrixx lyrixx commented May 5, 2026

PHP 8.2 and 8.3 are not supported anymore https://www.php.net/supported-versions.php

Note

We'll need to adapt CI rules directly in GitHub project configuration

@lyrixx lyrixx requested review from joelwurtz and pyrech and removed request for pyrech May 5, 2026 12:20
@lyrixx lyrixx requested a review from pyrech May 11, 2026 09:22
Copy link
Copy Markdown
Member

@pyrech pyrech left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just my 2 cents, it's a bit early IMO, these PHP versions are not EOL yet. I guess it's ok for Linux/MacOS that could instead use Castor binaries with PHP embeded, but not Windows ATM.

Anyway, we will also need to update the installer when we release this PR: https://github.com/jolicode/castor/blob/main/installer/bash-installer#L131-L135

@lyrixx
Copy link
Copy Markdown
Member Author

lyrixx commented May 12, 2026

They have not reached EOL yet. However, they are in 'security fixes only' mode.
Version 8.2 will reach EOL in seven months, and version 8.3 in one year and seven months.

Symfony 8.x requires PHP 8.4. It was released six months ago.

I think we could follow Symfony's lead, which would allow us to upgrade to Symfony 8.1 and leverage many new features (DIC, command upgrade, etc.).

Finally, PHP 8.4 and PHP 8.5 are available for Windows, so we won't prevent people from upgrading.

Those who cannot upgrade can stick to the current Castor version, which supports PHP 8.2.

TL;DR: Not upgrading to PHP 8.4+ blocks innovation.

Copy link
Copy Markdown
Member

@pyrech pyrech left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not ok with this requirement upgrade but the PR looks good to me anyway, so I leave it up to you 🙃

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants