chore: update legacy deps #8902
Merged
Conversation
This file contains hidden or 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
roxblnfk
reviewed
Aug 27, 2025
| "composer/semver": "^3.4", | ||
| "composer/xdebug-handler": "^3.0.5", | ||
| "fidry/cpu-core-counter": "^1.2", | ||
| "react/child-process": "^0.6.6", | ||
| "react/event-loop": "^1.0", | ||
| "react/promise": "^2.11 || ^3.0", |
There was a problem hiding this comment.
Is this change required for the project?
We stuck on promise v2 in our open source project because there are a lot of breaking changes and undesirable behavior in v3. And now it will be impossible to update CS fixer
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.
eg react/promise v2 is 2 years old
i'm eager to release it as separated patch and see if anyone upgraded to 3.85.0 but failed to upgrade to 3.85.1