-
Notifications
You must be signed in to change notification settings - Fork 72
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
Allow PHP 8 #201
Allow PHP 8 #201
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
https://github.com/maglnet/ComposerRequireChecker/pull/201/checks?check_run_id=1252051299#step:7:10
Seems like composer.lock
needs an update.
composer update nothing
could suffice
Ah, of course. I'm not used to having lockfiles in projects I contribute to. |
Ha, need to update my own dependencies now :D |
Just to be clear, those are only in place so that tools like phpcs, psalm, phpstan etc do not change randomly and report slightly different results :) |
Yeah, obviously. I was thinking about this as a library, when I should have been thinking about it as a project. |
Any updates on this? Is there anything I could do to get this done? |
I'd say #208 needs to happen first. What we got here is mostly dependency issues, for now. |
@martinssipenko just a rebase needed now :-) |
55e8f8b
to
ba1ebc7
Compare
Now we're waiting on webmozarts/glob#21 |
If there's a hold-up there, it seems like there's only one use of that dependency ( |
PHP 8 was released last week: I'd call "hold up" when it's February/March :-) |
I think @Firehed isn't completely off here. Maybe the dependency could be loosened/removed even if the pull request over there is merged. Fewer dependencies is (almost) always a good thing I think. |
|
@MidnightDesign could you add PHP8 to the matrix for the phar creation action? Then @OskarStark could test if his issue which he opened the last days is resolved via the phar that gets build in the CI process. I think this would be awesome 🥇 |
You mean in the GitHub Actions config, right? Will do. Would it be useful to add it to any other workflows? Do Psalm or PHPStan do something differently depending on the version? What about |
|
Can you help me out how to test this? Before I just installed the phar via PHIVE 🤔 |
@OskarStark make a new directory, add a |
I used: {
"name": "test/foo",
"type": "project",
"description": "Test",
"license": "proprietary",
"repositories": [
{
"type": "vcs",
"url": "https://github.com/MidnightDesign/ComposerRequireChecker.git"
}
],
"require": {
"maglnet/composer-require-checker": "dev-patch-1"
}
} ->
->
with
Looks good to me 👍 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🚢
Rolling out a release ASAP |
@Ocramius will 3.0 phar also be available for download from releases? |
No idea if that's automated, sorry: for now I released for the "traditional" approach, which allows most projects to start using the dependency again after upgrading to php 8 |
Ok, it requires manual steps: https://twitter.com/MaGlNet/status/1351079268831416323 I can't do a release, since my GPG key is not really part of that trust chain. |
All previous versions had phar files available, perhaps you could manually add them to release? This project works better if used as phar instead of |
Please re-read what I just wrote, slowly. |
Just read your last comment, after posting my previous one. Great! I'll keep an eye on it. Thanks! |
@martinssipenko |
Thank you! |
No description provided.