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 (v1.9.0) #747

Merged
merged 2 commits into from
Jul 1, 2024

Conversation

meili-bot
Copy link
Contributor

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

This PR:

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

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

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

@curquiza curquiza added the maintenance Anything related to maintenance (CI, tests, refactoring...) label Jun 5, 2024
@curquiza curquiza force-pushed the bump-meilisearch-v1.9.0 branch 5 times, most recently from b9fde83 to 61cc0af Compare June 5, 2024 16:01
@curquiza curquiza marked this pull request as ready for review July 1, 2024 11:33
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.

bors merge

Copy link
Contributor

meili-bors bot commented Jul 1, 2024

Build succeeded:

  • integration-and-unit-tests
  • linter

@meili-bors meili-bors bot merged commit 8eef84f into main Jul 1, 2024
3 of 4 checks passed
@meili-bors meili-bors bot deleted the bump-meilisearch-v1.9.0 branch July 1, 2024 11:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
maintenance Anything related to maintenance (CI, tests, refactoring...)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants