Run Travis CI for PHP 7.4 #83
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Also, it appears your Travis CI integration Github isn't working anymore. Older PRs still show the build status (in the overview page), but newer ones don't, yet builds are still triggered, see e.g. https://travis-ci.org/github/commerceguys/intl/builds/732018484. |
|
Looks like travis-ci.org is slowly dying, it's supposed to be turned off at the end of this year. I turned on the .com version but have no clue how to do a full migration yet. An adventure for another day. |
|
Thanks! |
|
@bojanz Yeah, Travis got a bit confusing recently. What worked for my repos was to "install" the Marketplace app. Good luck! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When I submitted #82 , I noticed Travis wasn't testing against PHP 7.4. This PR also lists PHP 7.4 (current stable) as test targets for Travis.
Reason why I created a separate PR is to address potential PHP 7.4 failures separately from the new features in my other PR. I hope that's oaky!