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) PHP8 Support #68

Merged
merged 13 commits into from
Dec 2, 2020
Merged

(Update) PHP8 Support #68

merged 13 commits into from
Dec 2, 2020

Conversation

HDVinnie
Copy link
Contributor

No description provided.

@HDVinnie
Copy link
Contributor Author

@owenvoke @Elhebert anyway this can be merged?

composer.json Outdated Show resolved Hide resolved
@owenvoke
Copy link
Contributor

Nice, I don't actually have any say in this package (I'm just a past contributor). But probably seems fine. Might be worth updating the CI workflows as well to run against PHP 8. 👍🏻 If you need any help with that, let me know.

HDVinnie and others added 3 commits November 29, 2020 21:21
@HDVinnie
Copy link
Contributor Author

@owenvoke thanks. Updated the PHPUnit configs and the composer.json with your suggestion.

@Elhebert
Copy link
Owner

Thanks for the PR, the code looks good. However some tests are failing due to some deprecation. Can you have a look?

@owenvoke
Copy link
Contributor

Looks like the depreciations are due to versions of Mockery lower than 1.4.1. 🤔

When running on the --prefer-lowest on PHP 8, it seems to select the exact version that is specified by orchestra/testbench-core, which for Testbench 4.5 is Mockery 1.2.3, not sure how to force that to be the latest version without adding Mockery ^1.4.2 to the Composer JSON.

@HDVinnie
Copy link
Contributor Author

Looks like the depreciations are due to versions of Mockery lower than 1.4.1. 🤔

When running on the --prefer-lowest on PHP 8, it seems to select the exact version that is specified by orchestra/testbench-core, which for Testbench 4.5 is Mockery 1.2.3, not sure how to force that to be the latest version without adding Mockery ^1.4.2 to the Composer JSON.

I have update tests and composer.json but IMO for them to all pass will need to drop PHP 7.2 support and only allow 7.3, 7.4 and 8.0.

@HDVinnie
Copy link
Contributor Author

@Elhebert all tests are now passing. Would mean the new release oof this package would require PHP 7.3+

@owenvoke
Copy link
Contributor

I feel like that's probably fine. PHP 7.2 is EOL, and people can still use the existing version perfectly fine if they are on 7.2. 🤔

@Elhebert
Copy link
Owner

Elhebert commented Dec 1, 2020

Do we still need to mockery as a dev dependency if we drop 7.2?

@HDVinnie
Copy link
Contributor Author

HDVinnie commented Dec 1, 2020

Do we still need to mockery as a dev dependency if we drop 7.2?

Yes for PHP8. New release of this package should be v3.0.0 and requires PHP 7.3+

@Elhebert
Copy link
Owner

Elhebert commented Dec 1, 2020

I already started work on a v3 (#57) which drop the support of Laravel 7 (and PHP 7.2.5).

I'm going to merge (soon) #62 and #65 into master. Once this is done, you can rebase and see if we still need to have mockery as a dev dependency or not.

I'll try to do it before the end of the day (in the next 6-8 hours).

That way we can release v3 with PHP8 support.

@owenvoke
Copy link
Contributor

owenvoke commented Dec 1, 2020

If it's Laravel 8+, that should be fine. 👍🏻

@Elhebert
Copy link
Owner

Elhebert commented Dec 1, 2020

@HDVinnie just merged both branches. You can now rebase on master ;)

@HDVinnie
Copy link
Contributor Author

HDVinnie commented Dec 1, 2020

@Elhebert PR is good to go.

@owenvoke
Copy link
Contributor

owenvoke commented Dec 1, 2020

Should be able to just do ^7.3 || ^8.0 for the PHP version. 👍🏻 Otherwise this looks great.

@@ -13,12 +13,13 @@
}
],
"require": {
"php": "^7.3",
"php": "^7.3 | ^7.4 | ^8.0",
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"php": "^7.3 | ^7.4 | ^8.0",
"php": "^7.3 || ^8.0",

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This does the same thing.....just comes down to personal preference. I always like clearly defining each version. If you dont then ill change it.

@Elhebert Elhebert merged commit cb60519 into Elhebert:master Dec 2, 2020
@Elhebert
Copy link
Owner

Elhebert commented Dec 2, 2020

v3 has been tagged and released 🎉

@HDVinnie HDVinnie deleted the patch-1 branch December 2, 2020 10:05
@thirsch thirsch mentioned this pull request Mar 23, 2021
Elhebert pushed a commit that referenced this pull request Mar 26, 2021
* (Update) PHP8 Support (#68)

* update: php8 support

* update: composer.json

Co-authored-by: Owen Voke <development@voke.dev>

* update: phpunit-l7.yml

* update: phpunit-l8.yml

* update: phpunit-l7.yml

* update: phpunit-l8.yml

* update: composer.json

* update: composer.json

* update: phpunit-l7.yml

* update: composer.json

* update: composer.json

- force latest mockery for PHP8

Co-authored-by: Owen Voke <development@voke.dev>

(cherry picked from commit cb60519)

* (Update) PHP8 Support (#68)

* update: php8 support

* update: composer.json

Co-authored-by: Owen Voke <development@voke.dev>

* update: phpunit-l7.yml

* update: phpunit-l8.yml

* update: phpunit-l7.yml

* update: phpunit-l8.yml

* update: composer.json

* update: composer.json

* update: phpunit-l7.yml

* update: composer.json

* update: composer.json

- force latest mockery for PHP8

Co-authored-by: Owen Voke <development@voke.dev>

(cherry picked from commit cb60519)

* Adjusted github actions.

* Adjusted minimum versions of laravel 6 and 7.

* Minimum version of mockery set.

* Min. mockery only on php 8 build?

Co-authored-by: HDVinnie <hdinnovations@protonmail.com>
Co-authored-by: Thomas A. Hirsch <thomas.hirsch@vema-eg.de>
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