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

fix: pull the latest in the CI instead of forcing the v1.11 #691

Merged
merged 1 commit into from
Oct 31, 2024

Conversation

mdubus
Copy link
Member

@mdubus mdubus commented Oct 30, 2024

Pull Request

Related issue

Fixes #690

What does this PR do?

Pull the latest in the CI instead of forcing the v1.11

PR checklist

Please check if your PR fulfills the following requirements:

  • Does this PR fix an existing issue, or have you listed the changes applied in the PR description (and why they are needed)?
  • Have you read the contributing guidelines?
  • Have you made sure that the title is accurate and descriptive of the changes?

Thank you so much for contributing to Meilisearch!

@mdubus mdubus added bug Something isn't working CI labels Oct 30, 2024
@mdubus
Copy link
Member Author

mdubus commented Oct 31, 2024

bors merge

@mdubus mdubus merged commit fc1115f into main Oct 31, 2024
28 checks passed
@mdubus mdubus deleted the revert_forcing_the_ci_to_v_1_11 branch October 31, 2024 09:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working CI
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Revert forcing the Meilisearch version to v1.11 instead of the latest
3 participants