Update version for the next release (v0.47.0)

[meili-bot]

This PR is auto-generated.

The automated script updates the version of meilisearch-js to a new version: "v0.47.0"

CHANGELOGS 👇

This version introduces features released on Meilisearch v1.12.0 🎉

Check out the Meilisearch v1.12.0 changelog for more information.

🚀 Enhancements

• Addition: Add methods to get batches #1775

Introducing new methods to get one or several batches, respectively getBatch() and getBatches().

// fetch one batch using batch UID
const batch = await client.getBatch(123)

// fetch all batches
const batches = await client.getBatches()

• Addition: Add reverse parameter to getTasks method #1774

The getTasks() methods now accept a reverse parameter to retrieve tasks in reverse chronological order.

const tasks = await client.getTasks({ reverse: true });

• Addition: Add new index settings to configure prefixSearch and facetSearch  #1790

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.

// disable prefix search
await client.index('myIndex').updatePrefixSearch('disabled')
// reset prefix search settings
await client.index('myIndex').resetPrefixSearch()

// disable facet search
await client.index('myIndex').updateFacetSearch(false)
// reset facet search settings
await client.index('myIndex').resetFacetSearch()

• Update: Add indices array to matches position #1773

The _matchesPosition array now contains an indices array the text was matched in an array.

When searching for fantasy in a document that has a searchable genre field with the value genre: ["fantasy", "adventure"], the matches position will be as follow:

{
  genre: [{ start: 0, length: 7, indices: [0] }]
}

Which means:

• There was a single match in the genre array (array length == 1)
• The match started as position 0 (the first character, "f")
• The match has a length of 7 (the entire "fantasy" word)
• The match was in the first item of the array (indices == [0])

⚙️ Maintenance/misc

• Update CONTRIBUTING.md with minimal Node version (Update CONTRIBUTING.md with minimal Node version #1788)

Thanks again to @/irevoire, @/Barabasbalazs, @/irevoire, @/curquiza, and @/Strift. 🎉

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.81%. Comparing base (756d856) to head (402163f).
Report is 80 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1797   +/-   ##
=======================================
  Coverage   97.81%   97.81%           
=======================================
  Files          17       17           
  Lines        1465     1465           
  Branches      307      307           
=======================================
  Hits         1433     1433           
  Misses         32       32           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[Strift]

Hey @mdubus @curquiza, I'm not sure who usually handles reviews for the changelogs so I tagged you both. 😬

[curquiza]

@Strift no need to tag Morgane here, only for coding PR 😊

Thank you for the changelog!

Some points

• Can you add missing sentence at the beginning saying this version is compatible with meilisearch v1.12? (check examples in other release specific to Meilisearch releases)
• Also, you did not put the already existing content of the draft of the release
• I think it's more useful for users to see how to use batch methods (like you did for getTasks) rather to see the batch object (not everyone uses typescript)

Also, thank you so much for all the details, but next time you can of course go shorter 😉 since our time is limited, the purpose is not to spend 15-30min on it. 5-10min is wayyy enough, you can be really quick. Focus on examples with library, don't explain the behavior of meilisearch, or the details of the typescript object. For any Meilisearch behavior, redirect to the changelogs

[Strift]

Hey @curquiza, thanks for the review.

Also, you did not put the already existing content of the draft of the release

Where can I find this please?

[curquiza]

Here: https://github.com/meilisearch/meilisearch-js/releases

[Strift]

I don't understand what you're expecting of me.

On the link you provided, I can only see the content for releases v0.46.1 and earlier, but nothing related to v0.47. Should I see something else?

What should I include in the v0.47 release notes?

[curquiza]

On the link you provided, I can only see the content for releases v0.46.1 and earlier, but nothing related to v0.47. Should I see something else?

You can only see v0.46.1, but it's a draft release, not an actual release (only you and maintainers can see it).
The automated release drafter put 0.46.1 and not 0.47.0 because so far, no PR has been released with breaking changes, so only the patch (3rd number) increased.

What should I include in the v0.47 release notes?

Yes, I need to be able to only copy/paste what you wrote in this comment during D-day (23rd December), without thinking more, to save time (it's a really busy day)

[Strift]

Okay, thanks for the explanation. I added the content of the draft release to the PR.

[curquiza]

Perfecto
⚠️ to merge next Monday only

[curquiza]

bors merge

[meili-bors]

Build succeeded:

• integration-tests (Node.js 20)
• style-check
• types-check
• integration-tests (Node.js 18)