Changes for supporting elasticpress 5.0.1 #2453
Open
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
aschmoe
force-pushed
the
elasticpress-5.0.1
branch
from
7ee378c
to
1056785
Compare
aschmoe
force-pushed
the
elasticpress-5.0.1
branch
2 times, most recently
from
3469bec
to
730dfdb
Compare
aschmoe
force-pushed
the
elasticpress-5.0.1
branch
from
730dfdb
to
918b546
Compare
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.
Updates for elasticpress in order to support the move to php 8.2
@TODOTracking#2428
wp-proud-search-elasticproudcity/wp-proud-search-elastic#3
Merging composer changes separately in #2603, need to get development cleaned up and updated here