fix: narrow serializable-closure conflict to only broken versions (2.0.9–2.0.10)#129
Merged
PabloKowalczyk merged 2 commits intoApr 12, 2026
Conversation
The conflict added in crunzphp#123 blocked all versions >=2.0.9, but v2.0.11 includes the upstream fix (laravel/serializable-closure#129). Narrow the constraint to >=2.0.9, <2.0.11 so only the two broken releases (v2.0.9 and v2.0.10) are blocked. Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
Member
|
Unfortunately CI failed |
Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
Contributor
Author
@PabloKowalczyk sorry about that. Should be fixed now. |
Member
|
Thanks @esetnik |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
laravel/serializable-closureconflict from>=2.0.9to>=2.0.9, <2.0.11, allowing v2.0.11+ which includes the upstream fixContext
PR #123 added a
conflictentry blocking>=2.0.9due to a regression inlaravel/serializable-closure(laravel/serializable-closure#126). That regression was fixed upstream in laravel/serializable-closure#129, which shipped in v2.0.11.The current blanket
>=2.0.9constraint blocks the fixed version too. This PR narrows it to only the two broken releases:Follow-up to #123.