-
-
Notifications
You must be signed in to change notification settings - Fork 14
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 thecodingmachine/safe 2 #142
Conversation
To prevent a lot of deprecation messages when running version 1 on PHP 8.4
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.
Need to review how best to move away from safe anyway in the long term. But for now can you also made sure composer.lock
is updated with composer update --lock
?
Aah, yeah, ofcourse, did not see the Tried to amend my last commit, feel free to squash commits to prevent GIT history pollution... |
@WyriHaximus thanks! Can this also be tagged as a release in the version 4 branch? I suppose 4.0.4? This library depends on it: https://github.com/WyriHaximus/reactphp-child-process-pool/blob/1ad9bc8c00e2dbebdd9559f57175b6f8eb86ce27/composer.json#L17 Which is used by: https://github.com/reactphp/filesystem/blob/766cdef9ba806367114f0c5ba36ea2a6eec8ccd2/composer.json#L19 ;) |
Not on this branch, this is for the upcoming v5. Could you create a PR for the 4.x branch so I can get a new v4 version out the door? |
Sure, see #143 |
@WyriHaximus you wrote:
Both This might be an interesting discussion though: thecodingmachine/safe#437 Then the following functions that use the Safe dependency remain (scanned quickly):
|
To prevent a lot of deprecation messages when running version 1 on PHP 8.4