Skip to content

Changes related to the next Meilisearch release (v1.14.0) #378

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 6 commits into from
Apr 15, 2025
Merged

Changes related to the next Meilisearch release (v1.14.0) #378

merged 6 commits into from
Apr 15, 2025

Conversation

meili-bot
Copy link
Contributor

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

This PR:

  • gathers the changes related to the next Meilisearch release (v1.14.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.14.0 is out.

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

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

@Strift Strift self-assigned this Apr 4, 2025
@Strift Strift requested a review from curquiza April 10, 2025 09:10
curquiza
curquiza approved these changes Apr 10, 2025
View reviewed changes
Copy link
Member

@curquiza curquiza left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅

@Strift Strift marked this pull request as ready for review April 15, 2025 02:09
@Strift Strift merged commit 9e6738b into main Apr 15, 2025
32 checks passed
@Strift Strift deleted the bump-meilisearch-v1.14.0 branch April 15, 2025 02:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@curquiza curquiza curquiza approved these changes

Assignees

@Strift Strift

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@meili-bot @curquiza @Strift