Update composer.json to allow liip/serializer 3.x#17
Merged
Conversation
liip/serializer 3.x does not update its SerializerInterface, or the Serializer/Deserializer in a significant way, so the adapter still works with it, and should be allowed to.
dbu
approved these changes
Apr 13, 2026
Member
dbu
left a comment
dbu
left a comment
There was a problem hiding this comment.
thanks a lot! i will release it as a patch release, we don't add features by allowing the serializer version 3.
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.
liip/serializer 3.x does not update its SerializerInterface, or the Serializer/Deserializer in a significant way, so the adapter still works with it, and should be allowed to.
What's in this PR?
This PR allows liip/serializer 3.x to be used with this adapter.
Why?
liip/serializer 3.x does not update its SerializerInterface, or the Serializer/Deserializer in a significant way, so the adapter still works with it. The current
composer.jsondisallows upgrading to the serializer 3.x, so this PR adds the 3.x top the constraints. I believe this causes no BC break by itself.Checklist