Update version for the next release (v0.51.0)

[meili-bot]

This PR is auto-generated.

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

Changelog

This version introduces features released in Meilisearch v1.15.0.

⚠️ Breaking changes

• Add disableOnNumbers to typo tolerance settings (Add disableOnNumbers to typo tolerance settings #1951) @\Strift
• Drop Node 18 support (Drop Node 18 support #1927) @\flevi29

🚀 Enhancements

• Add experimental features methods (Add experimental features methods #1928) @\flevi29
• export type GranularFilterableAttribute (chore: export type GranularFilterableAttribute #1965) @nicolasvienot

⚙️ Maintenance/misc

• Remove _md code samples for Mintlify migration (Remove _md code samples for Mintlify migration #1924) @\curquiza
• Trace Node.js warnings in CI tests (Trace Node.js warnings in CI tests #1946) @\flevi29
• Improve tasks and batch types, refactor related tests (Improve tasks and batches types, refactor related tests #1952) @\flevi29

Thanks again to @\curquiza, @\flevi29 and @Strift! 🎉

Summary by CodeRabbit

• Chores
  • Updated the application version to 0.51.0.

[coderabbitai]

Walkthrough

The changes update the package version from "0.50.0" to "0.51.0" in both the package.json file and the PACKAGE_VERSION constant within the codebase. No other modifications were made to dependencies, exports, or public entities.

Changes

File(s)	Change Summary
package.json	Updated version from "0.50.0" to "0.51.0"
src/package-version.ts	Updated PACKAGE_VERSION constant to "0.51.0"

Poem

A hop, a skip, a version jump,
From fifty to fifty-one we thump!
The number’s new, the code’s the same,
But every change deserves acclaim.
🐇✨ Version bumps, we celebrate—
Onward, upward, isn’t it great?

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d8d2abe and e3b2363.

📒 Files selected for processing (2)

• package.json (1 hunks)
• src/package-version.ts (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: integration-tests (Node.js 22)
• GitHub Check: integration-tests (Node.js 20)

🔇 Additional comments (3)

src/package-version.ts (1)

1-1: Version constant updated correctly
PACKAGE_VERSION has been bumped to "0.51.0" and is consistent with the value in package.json.

package.json (2)

3-3: Package version field updated correctly
The "version" field is now set to "0.51.0" and matches the exported constant in the code.

---

1-93:

✅ Verification successful

Verify no lingering old version references
Run a search to confirm that "0.50.0" doesn’t remain in docs, lock files, CI configs, or CHANGELOG.

---

🏁 Script executed:

#!/bin/bash
# Search for any remaining references to the old version
rg -n '"0\.50\.0"'

Length of output: 20

---

🏁 Script executed:

#!/bin/bash
# Re-run a broader search for any lingering references to the old version
rg -n '0\.50\.0' || true

# Additionally check common auxiliary files
for file in CHANGELOG.md yarn.lock package-lock.json; do
  if [ -f "$file" ]; then
    echo "Searching in $file"
    rg -n '0\.50\.0' "$file" || true
  fi
done

Length of output: 361

---

Verified: no lingering “0.50.0” references found
Search across the codebase, yarn.lock and package-lock.json yielded no matches for the previous version.

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.01%. Comparing base (fbd78d0) to head (ae1ed80).
Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1963   +/-   ##
=======================================
  Coverage   99.01%   99.01%           
=======================================
  Files          18       18           
  Lines        1418     1418           
  Branches      299      299           
=======================================
  Hits         1404     1404           
  Misses         14       14           

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.