-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes related to Meilisearch v1.7.0 #296
Labels
Meilisearch bump
Changes related to the Meilisearch bump version
Comments
curquiza
added
the
Meilisearch bump
Changes related to the Meilisearch bump version
label
Feb 12, 2024
curquiza
changed the title
Changes relateed to Meilisearch v1.7.0
Changes related to Meilisearch v1.7.0
Feb 13, 2024
This was referenced Feb 14, 2024
Merged
5 tasks
meili-bors bot
added a commit
to meilisearch/meilisearch-js
that referenced
this issue
Mar 11, 2024
1631: Changes related to the next Meilisearch release (v1.7.0) r=brunoocasali a=meili-bot Related to this issue: meilisearch/integration-guides#296 This PR: - gathers the changes related to the next Meilisearch release (v1.7.0) so that this package is ready when the official release is out. - should pass the tests against the [latest pre-release of Meilisearch](https://github.com/meilisearch/meilisearch/releases). - might eventually contain test failures until the Meilisearch v1.7.0 is out.⚠️ This PR should NOT be merged until the next release of Meilisearch (v1.7.0) is out. _This PR is auto-generated for the [pre-release week](https://github.com/meilisearch/integration-guides/blob/main/resources/pre-release-week.md) purpose._ Co-authored-by: meili-bot <74670311+meili-bot@users.noreply.github.com> Co-authored-by: nicolasvienot <nvienot@gmail.com> Co-authored-by: Clémentine U. - curqui <clementine@meilisearch.com> Co-authored-by: Bruno Casali <brunoocasali@gmail.com>
meili-bors bot
added a commit
to meilisearch/meilisearch-php
that referenced
this issue
Mar 11, 2024
617: Changes related to the next Meilisearch release (v1.7.0) r=curquiza a=meili-bot Related to this issue: meilisearch/integration-guides#296 This PR: - gathers the changes related to the next Meilisearch release (v1.7.0) so that this package is ready when the official release is out. - should pass the tests against the [latest pre-release of Meilisearch](https://github.com/meilisearch/meilisearch/releases). - might eventually contain test failures until the Meilisearch v1.7.0 is out.⚠️ This PR should NOT be merged until the next release of Meilisearch (v1.7.0) is out. _This PR is auto-generated for the [pre-release week](https://github.com/meilisearch/integration-guides/blob/main/resources/pre-release-week.md) purpose._ 621: Update version for the next release (v1.7.0) r=curquiza a=meili-bot _This PR is auto-generated._ The automated script updates the version of meilisearch-php to a new version: "v1.7.0" --- Part of this work #617 --- This version introduces features released on Meilisearch v1.7.0 🎉 Check out the changelog of [Meilisearch v1.7.0](https://github.com/meilisearch/meilisearch/releases/tag/v1.7.0) for more information on the changes. ##⚠️ Breaking changes * `scoreDetails` feature is not experimental anymore. You can directly use `showRankingScoreDetails` during a search without activating the experimental feature 🎉 ## 🚀 Enhancements * Includes any changes related to Hybrid search introduced in Meilisearch v1.7.0 🎉 ## ⚙️ Maintenance/misc * Added CodeCov coverage report support (#616) connorhu Co-authored-by: meili-bot <74670311+meili-bot@users.noreply.github.com> Co-authored-by: curquiza <clementine@meilisearch.com>
meili-bors bot
added a commit
to meilisearch/meilisearch-js-plugins
that referenced
this issue
Mar 11, 2024
1290: Changes related to the next Meilisearch release (v1.7.0) r=brunoocasali a=meili-bot Related to this issue: meilisearch/integration-guides#296 This PR: - gathers the changes related to the next Meilisearch release (v1.7.0) so that this package is ready when the official release is out. - should pass the tests against the [latest pre-release of Meilisearch](https://github.com/meilisearch/meilisearch/releases). - might eventually contain test failures until the Meilisearch v1.7.0 is out.⚠️ This PR should NOT be merged until the next release of Meilisearch (v1.7.0) is out. _This PR is auto-generated for the [pre-release week](https://github.com/meilisearch/integration-guides/blob/main/resources/pre-release-week.md) purpose._ Co-authored-by: meili-bot <74670311+meili-bot@users.noreply.github.com> Co-authored-by: curquiza <clementine@meilisearch.com>
meili-bors bot
added a commit
to meilisearch/meilisearch-python
that referenced
this issue
Mar 11, 2024
928: Changes related to the next Meilisearch release (v1.7.0) r=curquiza a=meili-bot Related to this issue: meilisearch/integration-guides#296 This PR: - gathers the changes related to the next Meilisearch release (v1.7.0) so that this package is ready when the official release is out. - should pass the tests against the [latest pre-release of Meilisearch](https://github.com/meilisearch/meilisearch/releases). - might eventually contain test failures until the Meilisearch v1.7.0 is out.⚠️ This PR should NOT be merged until the next release of Meilisearch (v1.7.0) is out. _This PR is auto-generated for the [pre-release week](https://github.com/meilisearch/integration-guides/blob/main/resources/pre-release-week.md) purpose._ 932: Update version for the next release (v0.31.0) r=curquiza a=meili-bot _This PR is auto-generated._ The automated script updates the version of meilisearch-python to a new version: "v0.31.0" --- Part of the work of #928 --- This version introduces features released on Meilisearch v1.7.0 🎉 Check out the changelog of [Meilisearch v1.7.0](https://github.com/meilisearch/meilisearch/releases/tag/v1.7.0) for more information on the changes. ##⚠️ Breaking changes * Related to the experimental `vectorStore` feature: `dimensions` field is now required when using OpenAI models. ## 🐛 Bug Fixes * Make embedders deseralize to correct type (#927) sanders41 ## ⚙️ Maintenance/misc * Update author (#931) `@curquiza` Co-authored-by: meili-bot <74670311+meili-bot@users.noreply.github.com> Co-authored-by: Paul Sanders <psanders1@gmail.com> Co-authored-by: Clémentine U. - curqui <clementine@meilisearch.com>
meili-bors bot
added a commit
to meilisearch/meilisearch-rust
that referenced
this issue
Mar 11, 2024
544: Changes related to the next Meilisearch release (v1.7.0) r=curquiza a=meili-bot Related to this issue: meilisearch/integration-guides#296 This PR: - gathers the changes related to the next Meilisearch release (v1.7.0) so that this package is ready when the official release is out. - should pass the tests against the [latest pre-release of Meilisearch](https://github.com/meilisearch/meilisearch/releases). - might eventually contain test failures until the Meilisearch v1.7.0 is out.⚠️ This PR should NOT be merged until the next release of Meilisearch (v1.7.0) is out. _This PR is auto-generated for the [pre-release week](https://github.com/meilisearch/integration-guides/blob/main/resources/pre-release-week.md) purpose._ Co-authored-by: meili-bot <74670311+meili-bot@users.noreply.github.com> Co-authored-by: curquiza <clementine@meilisearch.com> Co-authored-by: Clémentine U. - curqui <clementine@meilisearch.com>
meili-bors bot
added a commit
to meilisearch/meilisearch-php
that referenced
this issue
Mar 11, 2024
617: Changes related to the next Meilisearch release (v1.7.0) r=curquiza a=meili-bot Related to this issue: meilisearch/integration-guides#296 This PR: - gathers the changes related to the next Meilisearch release (v1.7.0) so that this package is ready when the official release is out. - should pass the tests against the [latest pre-release of Meilisearch](https://github.com/meilisearch/meilisearch/releases). - might eventually contain test failures until the Meilisearch v1.7.0 is out.⚠️ This PR should NOT be merged until the next release of Meilisearch (v1.7.0) is out. _This PR is auto-generated for the [pre-release week](https://github.com/meilisearch/integration-guides/blob/main/resources/pre-release-week.md) purpose._ Co-authored-by: meili-bot <74670311+meili-bot@users.noreply.github.com> Co-authored-by: curquiza <clementine@meilisearch.com>
meili-bors bot
added a commit
to meilisearch/meilisearch-python
that referenced
this issue
Mar 11, 2024
928: Changes related to the next Meilisearch release (v1.7.0) r=curquiza a=meili-bot Related to this issue: meilisearch/integration-guides#296 This PR: - gathers the changes related to the next Meilisearch release (v1.7.0) so that this package is ready when the official release is out. - should pass the tests against the [latest pre-release of Meilisearch](https://github.com/meilisearch/meilisearch/releases). - might eventually contain test failures until the Meilisearch v1.7.0 is out.⚠️ This PR should NOT be merged until the next release of Meilisearch (v1.7.0) is out. _This PR is auto-generated for the [pre-release week](https://github.com/meilisearch/integration-guides/blob/main/resources/pre-release-week.md) purpose._ Co-authored-by: meili-bot <74670311+meili-bot@users.noreply.github.com> Co-authored-by: Paul Sanders <psanders1@gmail.com> Co-authored-by: Clémentine U. - curqui <clementine@meilisearch.com>
meili-bors bot
added a commit
to meilisearch/meilisearch-dart
that referenced
this issue
Mar 11, 2024
375: Changes related to the next Meilisearch release (v1.7.0) r=curquiza a=meili-bot Related to this issue: meilisearch/integration-guides#296 This PR: - gathers the changes related to the next Meilisearch release (v1.7.0) so that this package is ready when the official release is out. - should pass the tests against the [latest pre-release of Meilisearch](https://github.com/meilisearch/meilisearch/releases). - might eventually contain test failures until the Meilisearch v1.7.0 is out.⚠️ This PR should NOT be merged until the next release of Meilisearch (v1.7.0) is out. _This PR is auto-generated for the [pre-release week](https://github.com/meilisearch/integration-guides/blob/main/resources/pre-release-week.md) purpose._ Co-authored-by: meili-bot <74670311+meili-bot@users.noreply.github.com> Co-authored-by: curquiza <clementine@meilisearch.com> Co-authored-by: Ahmed Fwela <ahmednfwela@bdaya-dev.com> Co-authored-by: Ahmed Fwela <63286031+ahmednfwela@users.noreply.github.com> Co-authored-by: Clémentine U. - curqui <clementine@meilisearch.com>
meili-bors bot
added a commit
to meilisearch/meilisearch-ruby
that referenced
this issue
Mar 11, 2024
520: Changes related to the next Meilisearch release (v1.7.0) r=curquiza a=meili-bot Related to this issue: meilisearch/integration-guides#296 This PR: - gathers the changes related to the next Meilisearch release (v1.7.0) so that this package is ready when the official release is out. - should pass the tests against the [latest pre-release of Meilisearch](https://github.com/meilisearch/meilisearch/releases). - might eventually contain test failures until the Meilisearch v1.7.0 is out.⚠️ This PR should NOT be merged until the next release of Meilisearch (v1.7.0) is out. _This PR is auto-generated for the [pre-release week](https://github.com/meilisearch/integration-guides/blob/main/resources/pre-release-week.md) purpose._ Co-authored-by: meili-bot <74670311+meili-bot@users.noreply.github.com> Co-authored-by: Clémentine U. - curqui <clementine@meilisearch.com> Co-authored-by: curquiza <clementine@meilisearch.com>
This was referenced Mar 12, 2024
Closed
Closed
Closed
Closed
Closing this issue since all the issues of missing features have been opened, and old issues updated in the different repositories well done everyone 🎉 |
meili-bors bot
added a commit
to meilisearch/meilisearch-ruby
that referenced
this issue
Mar 19, 2024
527: Update .code-samples.meilisearch.yaml for v1.7.0 r=brunoocasali a=curquiza Following https://github.com/meilisearch/documentation/blob/090717049e117ffaa3a54baa010883c1c5f90c31/.code-samples.meilisearch.yaml#L1095 and https://github.com/meilisearch/documentation/blob/090717049e117ffaa3a54baa010883c1c5f90c31/.code-samples.meilisearch.yaml#L1103C1-L1103C52 Related to meilisearch/integration-guides#296 Co-authored-by: Clémentine U. - curqui <clementine@meilisearch.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue gathers the changes related to the v1.7.0 of Meilisearch that will impact the integrations scope.
📅 Release date: 2024-03-11
Timelines & steps
Pre-release
Fill in the "What to implement?" section below in this issue.
scoreDetails
scoreDetails
scoreDetails
scoreDetails
Ruby -> NOT neededRelease day
scoreDetails
stabilizationscoreDetails
feature are up to date with this stabilization in different repositories (close them or update them)What to implement?
Stabilize
scoreDetails
experimental featureIssue: meilisearch/meilisearch#4359
showRankingScoreDetails
parameter was previously present as experimental since v1.3.0. The booleanscoreDetails
had to be activated astrue
in the/experimental-features
route to makeshowRankingScoreDetails
available.It means this feature is already available in some integrations.
Here is the details
Not present in
Already present in:
TODO
scoreDetails
scoreDetails
scoreDetails
+scoreDetails
in the code base -> butshowRankingScoreDetails
is NOT present in the libraryscoreDetails
mention in code base + update the commented testscoreDetails
in README + update testsThe following integrations will not have the feature available for the release day: Dotnet, Java, Go, Rust and Swift
Improvement with OpenAI model for Hybrid search
Issue: meilisearch/meilisearch#4394
Hybrid search & embedders are already available in some integrations 👇
But not in
dimensions
field is now available in theopenAi
embedder settingsExample:
TODO
dimensions
field work for OpenAi modelsdimensions
field work for OpenAi modelsThe following integrations will not have the Hybrid search feature, so the OpenAI improvements, available for the release day: Dart, Dotnet, Java, Go, Ruby, Rust and Swift
New
/logs
experimental routeRelated issue: meilisearch/meilisearch#4317
We will not implement anything in our SDKs because this new route is mostly an internal & debugging tool than a real usage in code base
The text was updated successfully, but these errors were encountered: