Skip to content
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 the next Meilisearch release (v0.30.0) #482

Merged
merged 30 commits into from
Feb 27, 2023

Conversation

meili-bot
Copy link
Contributor

@meili-bot meili-bot commented Nov 7, 2022

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

This PR:

  • gathers the changes related to the next Meilisearch release (v0.30.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 v0.30.0 is out.

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

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

Done:

@alallema alallema added the breaking-change The related changes are breaking for the users label Feb 21, 2023
@alallema alallema marked this pull request as ready for review February 27, 2023 15:32
brunoocasali
brunoocasali previously approved these changes Feb 27, 2023
Copy link
Member

@brunoocasali brunoocasali left a comment

Choose a reason for hiding this comment

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

LGTM!!!! 🍖

@alallema
Copy link
Contributor

bors merge

@bors
Copy link
Contributor

bors bot commented Feb 27, 2023

Build succeeded:

  • integration-and-unit-tests
  • linter

@bors bors bot merged commit 936e384 into main Feb 27, 2023
@bors bors bot deleted the bump-meilisearch-v0.30.0 branch February 27, 2023 16:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking-change The related changes are breaking for the users
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants