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

Raise PHP min requirements to 7.2 and update PHPUnit to 8.5 #97

Closed
wants to merge 3 commits into from

Conversation

stronk7
Copy link
Member

@stronk7 stronk7 commented May 9, 2021

This pull request updates PHPUnit (own tests) to version 8.5.x because it's the very first supporting PHP 8.

Also, explicitly we raise general requirements and declare PHP 7.0.x and 7.1.x unsupported. Both are very old PHP versions (EOL > 1y ago) and still, keeping support for PHP 7.2, all recent Moodle branches (34_STABLE and up) continue being supported by the tool (no matter that many of them (34, 35, 36, 36, 38) are out of support).

Still, if somebody needs a version of the tool working with PHP 7.0 or 7.1, they can continue using current 3.0.8 without too much trouble, just they won't be able to add PHP 8.0 at the same time.

Recommendation (to decide): Let's call to the next version 3.1.0 or 3.5.0 or `4.0.0, given there are noticeable changes in the supported versions.

Finally, a lot of components (composer) are updated with the bump of the min. PHP version, and some small adjustments have been applied to keep everything working. Plus all the PHPUnit 8.5 specific changes.

Another step towards PHP8 support happening @ #94

@stronk7 stronk7 changed the title Phpunit 85 Raise PHP min requirements to 7.2 and update PHPUnit to 8.5 May 9, 2021
@kabalin
Copy link
Member

kabalin commented May 10, 2021

I totally agree regarding major version bump for release. Can you rebase it please @stronk7, so codefixer commit is not added.

And, also, raising PHP requirement to 7.2 in general
all branches since Moodle 3.4 can use that PHP version
so it's quite generous, specially when a bunch of them
(34, 35, 36, 37, 38) are completely out of support.

It comes with some other products updated too, so fixing
at the same time all the new psalm detections found
within moodle-plugin-ci
They can be left as far as many are only deprecations,
but better update all them to new counterparts towards
easier future updates.
Also, bump to ubuntu-18.04, dist files already are recommending it,
hence not change needed there, only own tests.

This closes moodlehq#96.
@stronk7
Copy link
Member Author

stronk7 commented May 10, 2021

Sure, now that #95 has been merged, going to rebuild this, pointing to the new incoming version... will comment once ready...

@stronk7
Copy link
Member Author

stronk7 commented May 11, 2021

Ok, I've been doing some more tests... and with a couple of issues fixed in codechecker/moodlecheck/ci... I think that we can make moodle-plugin-ci current v3 to run php8 tests... still testing... but just setting "max_input_vars=5000" may be enough.

Of course, that doesn't enable own tests to pass with php8, for that we need this issue and surely others...

But, I think that it's better to:

  1. Verify that v3 goes ok with php8 and perform some minor release with all the detected problems solved. So people will be able to switch to php8 without changing of version.

  2. Continue working towards v4, maybe in another branch, adding this issue and any other needed towards the bump in requirements and self-testing with php8 available.

How does that sound?

For now... I'm going to keep this on hold... and concentrate on verifying that a minor is enough (aka, point 1). So we can make a minor release providing that.

@scara
Copy link

scara commented May 12, 2021

How does that sound?

👍

HTH,
Matteo

@stronk7
Copy link
Member Author

stronk7 commented Jan 18, 2022

I'm going to close this in favour of #151, where the new moodle-plugin-ci, with raised requirements, will be planned.

@stronk7 stronk7 closed this Jan 18, 2022
@stronk7 stronk7 deleted the phpunit_85 branch January 17, 2023 22:28
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.

3 participants