Allow doctrine/persistence 3.1 version #1300
Merged
Conversation
This file contains 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
This was referenced May 4, 2023
|
@makasim should we just re-run CI workflow? It looks like a environment problems not related to the changes I've made? |
|
@makasim bump :) sorry for pushing this but I really need this changes |
|
Sorry, I can merge only completely green pipeline |
Sure, but can you trigger re-run? I hope so it's failing not due to the code changes |
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.
Currently on Symfony 6.2 there is an issue related to the doctrine/persistence. Symfony recommends to use the doctrine/persistence in the latest version 3.1 to use of lazy ghost objects.
It's also related to the ecotone that is using enqueue: ecotoneframework/ecotone-dev#111
@makasim