Update version for the next release (v0.20.0) #366
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
brunoocasali
added
the
breaking-change
brunoocasali
requested review from
alallema,
bidoubiwa and
curquiza
and removed request for
bidoubiwa
|
bors merge |
|
bors cancel |
meili-bors bot
added a commit
that referenced
this pull request
Sep 20, 2022
366: Update version for the next release (v0.20.0) r=brunoocasali a=brunoocasali This version makes this package compatible with Meilisearch v0.29.0 🎉 Check out the changelog of [Meilisearch v0.29.0](https://github.com/meilisearch/meilisearch/releases/tag/v0.29.0) for more information on the changes. ## 🚀 Enhancements - Ensure support to the new search query parameter `matchingStrategy` (#364) `@brunoocasali` - Ensure support to keys with wildcarded actions. - `actions` field during key creation now accepts wildcards on actions. For example, `indexes.*` provides rights to `indexes.create`, `indexes.get`,`indexes.delete`, `indexes.delete`, and `indexes.update`. (#365) `@brunoocasali` ##⚠️ Breaking Changes This breaking change *__may not affect you__*, but in any case, you should check your search queries if you want to keep the same behavior from `v0.28`. - The `NOT` filter keyword does not have an implicitly `EXIST` operator anymore. Check out for more information: meilisearch/meilisearch#2486 Co-authored-by: Bruno Casali <brunoocasali@gmail.com>
|
Canceled. |
curquiza
requested changes
Sep 20, 2022
curquiza
approved these changes
Sep 22, 2022
There was a problem hiding this comment.
Discussed with @brunoocasali
I understood how it could be useful to increase the major instead of increasing the patch even if it's not the "official" definition of semver 😊
A guide describing your versioning policy could be even better 🔥
|
bors merge |
|
Thanks again for contributing with Meilisearch ❤️ |
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.
This version makes this package compatible with Meilisearch v0.29.0 🎉
Check out the changelog of Meilisearch v0.29.0 for more information on the changes.
🚀 Enhancements
matchingStrategy(Add tests to custom search withmatching_strategyparam #364) @brunoocasaliactionsfield during key creation now accepts wildcards on actions. For example,indexes.*provides rights toindexes.create,indexes.get,indexes.delete,indexes.delete, andindexes.update. (Add tests to wildcarded action keys #365) @brunoocasaliThis breaking change may not affect you, but in any case, you should check your search queries if you want to keep the same behavior from
v0.28.NOTfilter keyword does not have an implicitlyEXISToperator anymore. Check out for more information: Rework theNOTfilter keyword meilisearch#2486