Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GH Actions: stop testing with PHP 8.4 against Composer < current #219

Merged
merged 1 commit into from
May 6, 2024

Conversation

jrfnl
Copy link
Member

@jrfnl jrfnl commented May 3, 2024

Proposed Changes

Composer 1.x is no longer supported and while Composer 2.2 is an LTS version, the LTS is only for critical bugs and security issues, not necessarily for supporting new PHP versions.

The LTS support was also officially only in effect until end of 2023 (and I have not seen any announcement of an extension).

In practice, this means the following:

  • Composer 1.x and Composer 2.2. were previously made compatible with PHP 8.2 and 8.3 (released since the announcement).
  • However, it is unlikely that Composer 1.x and Composer 2.2 will be made compatible with PHP 8.4 and builds against those combinations are already failing.

With the above in mind, I propose to stop running the tests against Composer 1.x/2.2 - PHP 8.4 combinations as they can only fail and those failures are not related to the plugin and outside our sphere of influence to fix.

This commit updates the integrationtest workflow to put the above into effect.

The quicktest workflow is currently not (yet) affected, but will be once PHP "latest" becomes PHP 8.4 towards the end of the year. At that time, a tweak will need to be made to the quicktest workflow as well.

Ref:

Composer 1.x is no longer supported and while Composer 2.2 is an LTS version, the LTS is only for critical bugs and security issues, not necessarily for supporting new PHP versions.

The LTS support was also officially only in effect until end of 2023 (and I have not seen any announcement of an extension).

In practice, this means the following:
* Composer 1.x and Composer 2.2. were previously made compatible with PHP 8.2 and 8.3 (released since the announcement).
* However, it is unlikely that Composer 1.x and Composer 2.2 will be made compatible with PHP 8.4 and builds against those combinations are already failing.

With the above in mind, I propose to stop running the tests against Composer 1.x/2.2 - PHP 8.4 combinations as they can only fail and those failures are not related to the plugin and outside our sphere of influence to fix.

This commit updates the `integrationtest` workflow to put the above into effect.

The `quicktest` workflow is currently not (yet) affected, but will be once PHP "latest" becomes PHP 8.4 towards the end of the year. At that time, a tweak will need to be made to the quicktest workflow as well.

Ref:
* composer/composer#10340
@Potherca Potherca merged commit a737e79 into main May 6, 2024
98 checks passed
@Potherca Potherca deleted the feature/ghactions-test-php-8.4-only-against-latest branch May 6, 2024 08:16
@Potherca
Copy link
Member

Potherca commented May 6, 2024

@jrfnl Great work! (as usual 😁 )

@fredden Thanks for reading along, much appreciated!

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

Successfully merging this pull request may close these issues.

3 participants