-
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.12.0 #307
Labels
Meilisearch bump
Changes related to the Meilisearch bump version
Comments
curquiza
added
the
Meilisearch bump
Changes related to the Meilisearch bump version
label
Nov 26, 2024
This was referenced Nov 26, 2024
Merged
This was referenced Nov 26, 2024
This was referenced Dec 16, 2024
meili-bors bot
added a commit
to meilisearch/meilisearch-kubernetes
that referenced
this issue
Dec 23, 2024
243: Changes related to the next Meilisearch release (v1.12.0) r=brunoocasali a=meili-bot Related to this issue: meilisearch/integration-guides#307⚠️ This PR should NOT be merged until the next release of Meilisearch (v1.12.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: Clémentine <[email protected]> Co-authored-by: Bruno Casali <[email protected]> Co-authored-by: Bruno Casali <[email protected]> Co-authored-by: brunoocasali <[email protected]>
meili-bors bot
added a commit
to meilisearch/meilisearch-js
that referenced
this issue
Dec 23, 2024
1768: Changes related to the next Meilisearch release (v1.12.0) r=curquiza a=meili-bot Related to this issue: meilisearch/integration-guides#307 This PR: - gathers the changes related to the next Meilisearch release (v1.12.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.12.0 is out.⚠️ This PR should NOT be merged until the next release of Meilisearch (v1.12.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: Strift <[email protected]> Co-authored-by: Clémentine <[email protected]> Co-authored-by: Laurent Cazanove <[email protected]> Co-authored-by: Balazs Barabas <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
meili-bors bot
added a commit
to meilisearch/meilisearch-php
that referenced
this issue
Dec 23, 2024
692: Changes related to the next Meilisearch release (v1.12.0) r=curquiza a=meili-bot Related to this issue: meilisearch/integration-guides#307 This PR: - gathers the changes related to the next Meilisearch release (v1.12.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.12.0 is out.⚠️ This PR should NOT be merged until the next release of Meilisearch (v1.12.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._ 705: Update version for the next release (v1.12.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.12.0" CHANGELOGS 👇 This version introduces features released on Meilisearch v1.12.0 🎉 Check out the [Meilisearch v1.12.0 changelog](https://github.com/meilisearch/meilisearch/releases/tag/v1.12.0) for more information. ## 🚀 Enhancements - **Addition:** #699 Introducing new methods to get one or several batches, respectively `getBatch()` and `getBatches()`. A batch is a set of tasks processed together. - **Addition:** #698 The `TaskQuery` class now has a `setReverse()` method to retrieve tasks in reverse chronological order. ```php client->getTasks((new TasksQuery())->setReverse(true)); ``` - **Addition:** #702 Index settings now allow disabling **prefix search** and **facet search**. They're both enabled by default. The SDK now comes with dedicated methods to configure these settings. ```php // disable prefix search $index->updatePrefixSearch('disabled'); // reset prefix search settings $index->resetPrefixSearch(); // disable facet search $index->updateFacetSearch(false); // reset facet search settings $index->resetFacetSearch(); ``` ## 🐛 Bug Fixes - fix: pull the latest in the CI instead of forcing the v1.11 (#691) `@/mdubus` - Make `hitsCount` always the number of `hits` (and not `totalHits` value) (#701) `@/johnnynotsolucky` ## ⚙️ Maintenance/misc - Update CI to run with PHP 8.4 (#696) `@/norkunas` - Fixed SearchNestedFieldsTest test (#704) `@/aivchen` - PHPStan 2 + fixed uninitialized properties in SearchResult (#706) `@/aivchen` Thanks again to `@/aivchen,` `@/johnnynotsolucky,` `@/mdubus,` `@/norkunas,` Andrei Ivchenkov, and `@/Strift!` 🎉 Co-authored-by: meili-bot <[email protected]> Co-authored-by: Clémentine <[email protected]> Co-authored-by: Strift <[email protected]> Co-authored-by: Laurent Cazanove <[email protected]>
meili-bors bot
added a commit
to meilisearch/meilisearch-php
that referenced
this issue
Dec 23, 2024
692: Changes related to the next Meilisearch release (v1.12.0) r=curquiza a=meili-bot Related to this issue: meilisearch/integration-guides#307 This PR: - gathers the changes related to the next Meilisearch release (v1.12.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.12.0 is out.⚠️ This PR should NOT be merged until the next release of Meilisearch (v1.12.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: Clémentine <[email protected]> Co-authored-by: Strift <[email protected]> Co-authored-by: Laurent Cazanove <[email protected]>
meili-bors bot
added a commit
to meilisearch/meilisearch-ruby
that referenced
this issue
Dec 23, 2024
575: Changes related to the next Meilisearch release (v1.12.0) r=curquiza a=meili-bot Related to this issue: meilisearch/integration-guides#307 This PR: - gathers the changes related to the next Meilisearch release (v1.12.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.12.0 is out.⚠️ This PR should NOT be merged until the next release of Meilisearch (v1.12.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: Louis Dureuil <[email protected]> Co-authored-by: Clémentine <[email protected]>
meili-bors bot
added a commit
to meilisearch/meilisearch-php
that referenced
this issue
Dec 23, 2024
692: Changes related to the next Meilisearch release (v1.12.0) r=curquiza a=meili-bot Related to this issue: meilisearch/integration-guides#307 This PR: - gathers the changes related to the next Meilisearch release (v1.12.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.12.0 is out.⚠️ This PR should NOT be merged until the next release of Meilisearch (v1.12.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: Clémentine <[email protected]> Co-authored-by: Strift <[email protected]> Co-authored-by: Laurent Cazanove <[email protected]>
This was referenced Dec 27, 2024
This was referenced Dec 31, 2024
Closing the issue, everything is dooooone 😁 |
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.12.0 of Meilisearch that will impact the integrations scope.
📅 Release date: 2024-12-23
Timelines & steps
Pre-release
Release day
What to implement?
Opt-out settings
Related issue in the engine: meilisearch/meilisearch#4979
Add index settings to customize indexing of users:
facetSearch
,prefixSearch
.TODO:
facetSearch
&prefixSearch
meilisearch-js#1770facetSearch
&prefixSearch
meilisearch-php#694Parameter to reverse the order of the task queue
Related issue in the engine: meilisearch/meilisearch#5047
Add a new parameter in
GET /tasks
route:reverse
TODO:
reverse
parameter when querying tasks meilisearch-js#1769reverse
parameter when querying tasks meilisearch-php#693Give more visibility around batch when indexing
Related issue in the engine:
progress
part of the batches meilisearch#5068Changes:
batchUid
.GET /batches/:uid
GET /batches
TODO:
progress
field in batch object meilisearch-js#1798progress
field in batch object meilisearch-php#708New field in
_matchPosition
Related PR: meilisearch/meilisearch#5005
Add a new
indices
field in the_matchesPosition
response.TODO:
indices
in_matchesPosition
meilisearch-js#1772Highlight changes
Related to this PR: meilisearch/meilisearch#4928
The above PR led to changes in highlight behavior (checked internally with the engine team, these are expected). We need to adapt the tests of instant-meilisearch
TODO
AI changes
Related PR: meilisearch/meilisearch#4900
Some tests in some SDKs have to be updated because of breaking changes
The text was updated successfully, but these errors were encountered: