-
Notifications
You must be signed in to change notification settings - Fork 90
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 the next Meilisearch release (v1.7.0) #1631
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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1631 +/- ##
=======================================
Coverage 97.52% 97.52%
=======================================
Files 22 22
Lines 850 850
Branches 109 102 -7
=======================================
Hits 829 829
Misses 20 20
Partials 1 1 ☔ View full report in Codecov by Sentry. |
5 tasks
5 tasks
brunoocasali
previously approved these changes
Mar 7, 2024
Add code samples to v1.7
curquiza
requested changes
Mar 7, 2024
Co-authored-by: Clémentine U. - curqui <[email protected]>
brunoocasali
approved these changes
Mar 11, 2024
bors merge |
meili-bors bot
added a commit
that referenced
this pull request
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 <[email protected]> Co-authored-by: nicolasvienot <[email protected]> Co-authored-by: Clémentine U. - curqui <[email protected]> Co-authored-by: Bruno Casali <[email protected]>
This PR was included in a batch that successfully built, but then failed to merge into main. It will not be retried. Additional information: {"message":"1 review requesting changes and 1 approving review by reviewers with write access.","documentation_url":"https://docs.github.com/articles/about-protected-branches"} |
meili-bors bot
added a commit
that referenced
this pull request
Mar 11, 2024
1633: Update version for the next release (v0.38.0) r=brunoocasali a=meili-bot _This PR is auto-generated._ The automated script updates the version of meilisearch-js to a new version: "v0.38.0" Part of the work of #1631 --- 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.⚠️ If you want to adopt new features of this release, **update the Meilisearch server** to the according version. ##⚠️ Breaking changes * Update Node.js versions that are used in tests (#1620) `@flevi29` * `scoreDetails` feature is not experimental anymore. You can directly use `showRankingScoreDetails` during a search without activating the experimental feature 🎉 ## 🚀 Enhancements * `dimensions` field is available to the OpenAi model (#1631) `@nicolasvienot` * Enable limit and offset according to documentation. (#1630) `@reijovosu` Co-authored-by: meili-bot <[email protected]>
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.
Related to this issue: meilisearch/integration-guides#296
This PR:
This PR is auto-generated for the pre-release week purpose.