Skip to content

Changes related to Meilisearch v1.15.0 #1388

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

Merged
merged 3 commits into from
Jun 10, 2025
Merged

Conversation

meili-bot
Copy link
Contributor

@meili-bot meili-bot commented May 23, 2025

Related to this issue: meilisearch/integration-guides#316

This PR:

  • gathers the changes related to the next Meilisearch release (v1.15.0) so that this package is ready when the official release is out.
  • should pass the tests against the latest pre-release of Meilisearch.
  • might eventually contain test failures until the Meilisearch v1.15.0 is out.

⚠️ This PR should NOT be merged until the next release of Meilisearch (v1.15.0) is out.

This PR is auto-generated for the pre-release week purpose.

Summary by CodeRabbit

  • Chores
    • Updated the Meilisearch dependency to version 0.51.

@meili-bot meili-bot added the skip-changelog The PR will not appear in the release changelogs label May 23, 2025
Copy link

changeset-bot bot commented May 23, 2025

🦋 Changeset detected

Latest commit: ff5c87e

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@meilisearch/instant-meilisearch Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Copy link

coderabbitai bot commented May 23, 2025

Walkthrough

This update documents and implements an upgrade of the Meilisearch dependency from version 0.50 to 0.51 in the @meilisearch/instant-meilisearch package. The change is recorded in a new changeset file, and no other code or logic modifications are included.

Changes

File(s) Change Summary
packages/instant-meilisearch/package.json Updated Meilisearch dependency version from 0.50 to 0.51.
.changeset/smooth-windows-matter.md Added changeset documenting the minor version bump.

Poem

A hop and a skip, a version anew,
Meilisearch hops from fifty to fifty-one too!
The changes are small, the docs are neat,
With every update, our search feels complete.
🐇✨


📜 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 1823e18 and ff5c87e.

⛔ Files ignored due to path filters (1)
  • yarn.lock is excluded by !**/yarn.lock, !**/*.lock
📒 Files selected for processing (2)
  • .changeset/smooth-windows-matter.md (1 hunks)
  • packages/instant-meilisearch/package.json (1 hunks)
🔇 Additional comments (2)
packages/instant-meilisearch/package.json (1)

47-47:

❓ Verification inconclusive

Upgrade Meilisearch dependency to 0.51
The dependency bump aligns with the upcoming Meilisearch v1.15.0 release. Ensure that your integration tests against the pre-release pass, and update any docs or examples that reference the Meilisearch version.

Run these commands to verify the version exists on npm and smoke-test compatibility:


🏁 Script executed:

npm view [email protected] version
npm install [email protected] --no-save && npm test

Length of output: 1611


Verify Meilisearch 0.51.0 Integration Compatibility
We confirmed that [email protected] is published on npm and installs without immediate errors. However, the smoke-test output didn’t include explicit test results. Please manually verify that:

  • Integration tests against Meilisearch v0.51.0 all pass
  • Any examples or documentation referencing the Meilisearch version are updated accordingly
.changeset/smooth-windows-matter.md (1)

1-6: Record a minor bump changeset
The changeset accurately captures the minor bump for @meilisearch/instant-meilisearch. Remember to merge this only after the official Meilisearch v1.15.0 release is published and regenerate the lockfile if necessary.


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
🪧 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.

@Strift Strift self-assigned this May 23, 2025
@Strift Strift marked this pull request as ready for review June 10, 2025 05:15
@Strift Strift changed the title Changes related to the next Meilisearch release (v1.15.0) Changes related to Meilisearch v1.15.0 Jun 10, 2025
@Strift Strift added this pull request to the merge queue Jun 10, 2025
@Strift Strift merged commit 9bcef24 into main Jun 10, 2025
12 checks passed
@Strift Strift deleted the bump-meilisearch-v1.15.0 branch June 10, 2025 05:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
skip-changelog The PR will not appear in the release changelogs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants