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: update for branch-cut of PHP 8.4 #208

Merged
merged 1 commit into from
Nov 7, 2024

Conversation

jrfnl
Copy link
Collaborator

@jrfnl jrfnl commented Nov 7, 2024

The branch for the new PHP (8.4) version has been cut, which means that PHP "nightly" is now PHP 8.5, so we need to add explicit builds to continue testing against PHP 8.4.

Builds against PHP 8.4 should also no longer be allowed to fail as this tool is used in CI, so, even though PHP 8.4 has not been released yet, 8.4 is not added to the continue-on-error setting.

Also see #180 for reasoning about why the explicit PHP 8.4 build is added "early".

The branch for the new PHP (8.4) version has been cut, which means that PHP "nightly" is now PHP 8.5, so we need to add explicit builds to continue testing against PHP 8.4.

Builds against PHP 8.4 should also no longer be allowed to fail as this tool is used in CI, so, even though PHP 8.4 has not been released yet, `8.4` is **not** added to the `continue-on-error` setting.

Also see 180 for reasoning about why the explicit PHP 8.4 build is added "early".
@coveralls
Copy link

coveralls commented Nov 7, 2024

Coverage Status

coverage: 96.408%. remained the same
when pulling 400a93c on JRF/ghactions/dont-fail-on-8.4
into a4a261f on 1.x.

@jrfnl jrfnl force-pushed the JRF/ghactions/dont-fail-on-8.4 branch from 66feedd to 400a93c Compare November 7, 2024 13:15
@jrfnl jrfnl merged commit 624efa1 into 1.x Nov 7, 2024
166 checks passed
@jrfnl jrfnl deleted the JRF/ghactions/dont-fail-on-8.4 branch November 7, 2024 13:19
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.

2 participants