chore: Upgrade Elasticsearch dependencies and update client usage for compatibility with v8.15.3 #3421
+33,753
−33,588
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
… compatibility with v8.15.3
|
@LeftoversTodayAppAdmin is attempting to deploy a commit to the Vendure Team on Vercel. A member of the Team first needs to authorize it. |
…rkflows and templates
… workflows and templates
|
Hey folks! |
|
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.
Description
Vendure has had a limitation on the version of ElasticSearch that can be used because of a licensing issue in v7.11 which has since been resolved. Therefore we can now use v8.15.3 as long as the plugin and the Vendure project use the new ES deployment and matching library.
Breaking changes
Does this PR include any breaking changes we should be aware of?
Does this PR include any breaking changes we should be aware of?
Users can continue using their existing ES instance and plugin without issues if they keep the older v7.10.2 ES library in their Vendure project's package.json.
Upgrading ElasticSearch is a one-way process, migrating the DB schema from v7.10.2 to v8.15.3 with no option to downgrade.
The ES library in both the plugin and Vendure project package.json must match the upgraded ES instance version (v8.15.3).
Screenshots
You can add screenshots here if applicable.
Checklist
📌 Always:
👍 Most of the time: