Update MeiliSearch to v1.1 #789
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
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.
Fixes #747
This updates the dev container and the test deployment to MeiliSearch v1.1. Doing this update before Tobira 2.0 is a good idea as this bundles all the non-trivial update steps into one release. Updating to a 1.x version is also useful as Meili is forward compatible to other 1.x releases now. So system administrators can update Meili independently from Tobira, if they want to.
I chose 1.1 instead of 1.0 for no particular reason. We don't currently need features from 1.1 in Tobira and I don't see this changing. However, it doesn't hurt just demanding 1.1 since admins have to update anyway. So if we need an 1.1 feature in the future, we can just use it.
Luckily, the update was painless and I hardly needed to adjust anything. Everything still seems to work.