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

Update minimum requirements and phpunit #357

Merged
merged 3 commits into from Nov 7, 2021
Merged

Update minimum requirements and phpunit #357

merged 3 commits into from Nov 7, 2021

Conversation

tacman
Copy link
Contributor

@tacman tacman commented Nov 5, 2021

PHP less than 7.2 is no longer supported (and 7.2 will be at EOL in a few weeks).

Bumping to PHP 7 also allows a more current phpunit.

@paxter
Copy link

paxter commented Nov 5, 2021

PHP less than 7.2 is no longer supported (and 7.2 will be at EOL in a few weeks).

Ending PHP support has nothing to do with supported PHP versions by this project. This project still works with PHP 5.3 so the provided version is correct.

@michelf
Copy link
Owner

michelf commented Nov 6, 2021

Scrutinizer tests are failing because it tests things with PHP 7.0.x. Perhaps you should edit the Scrutinizer configuration file as part of this pull request.

@paxter is right: we can still support down to PHP 5.3, although I'll admit it's probably not that useful at this point. Are you proposing this change because you're planning on doing things that depend on a newer version of PHPUnit?

@tacman
Copy link
Contributor Author

tacman commented Nov 6, 2021 via email

@michaelbutler
Copy link
Contributor

Hmm. This might be a worthwhile reason to modernize a bit. Phpunit not running anymore on 8.0 could introduce risk on any future changes made. Personally I think it could also invigorate more involvement in the project.

Remember that current versions on the library will continue to work with old PHP versions forever, just not future changes. It's just a matter of bumping the major composer version.

@michelf
Copy link
Owner

michelf commented Nov 6, 2021

Ok, let's do this. Type hints sound enticing, so 7.4.

@tacman
Copy link
Contributor Author

tacman commented Nov 6, 2021 via email

@tacman
Copy link
Contributor Author

tacman commented Nov 6, 2021 via email

@michaelbutler
Copy link
Contributor

String looks cool but unless there is a specific need for it, or problem it solves, I would say let's not integrate it.

Instead of moving to github actions we could just migrate to travis-ci.com (instead of .org) which should be a no-code change, @michelf just has to log in to travis-ci.com and click a few buttons to activate it on this repo (it'll see the existing travis.yml and nothing else is needed). I guess the old traivs-ci.org connection was killed which is why it isn't running on PRs?

This is just my personal opinion, but something doesn't sit right with doing everything under the GitHub (now Microsoft) umbrella... who knows how long it will be free for free/open source projects.

@michelf
Copy link
Owner

michelf commented Nov 6, 2021

@michaelbutler I'm not really following Travis-CI related news, but it looks like .org is more or less shutting down and .com is the replacement. And .com wants me to pick a plan and link a credit card, so I'm not sure I want to continue using Travis-CI.

@michaelbutler
Copy link
Contributor

well if travis .com is asking for a credit card my recommendation is not to use it 😄 I was pretty sure it is free but if they require a credit card (maybe to thwart spam abuse) that's too bad. GitHub actions is probably the way to go then.

@michelf michelf merged commit 169de84 into michelf:lib Nov 7, 2021
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.

None yet

4 participants