Use Meilisearch enterprise edition

[Strift]

Starting from Meilisearch v1.28, the community and enterprise editions of Meilisearch have distinct binaries.

To allow full-feature coverage, this PR updates the repository to test against the enterprise edition instead of the default community edition by using the getmeili/meilisearch-enterprise Docker image.

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!

Summary by CodeRabbit

• Chores

  • Updated service Docker image to enterprise edition across all deployment configurations and scripts.
  • Normalized string formatting in workflow configurations for consistency.

• Documentation

  • Updated contribution guidelines with enterprise Docker image references.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

This PR updates Docker image references from the community edition (getmeili/meilisearch) to the enterprise edition (getmeili/meilisearch-enterprise) across configuration files, scripts, and documentation. Minor quote normalization to double quotes is applied in one workflow file.

Changes

Cohort / File(s)	Summary
Docker configuration files docker-compose.yaml, resources/docker/docker-compose.yaml	Meilisearch service image updated from getmeili/meilisearch:latest to getmeili/meilisearch-enterprise:latest
GitHub scripts and workflows .github/scripts/beta-docker-version.sh, .github/workflows/cypress.yml	Docker repository endpoint and service image changed to enterprise edition; quote literals normalized to double quotes in workflow file
Documentation CONTRIBUTING.md	Docker pull and run commands updated to reference enterprise edition image

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

These are straightforward configuration updates with repetitive, consistent patterns across files—primarily image tag replacements and minor quote normalization.

Poem

🐰 From community to enterprise we hop,
Docker images switched, a simple swap,
Quotes aligned, the config refined,
Enterprise edition's now in mind!
A leap forward, our systems aligned. 🚀

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Use Meilisearch enterprise edition' clearly summarizes the main change across all modified files, which consistently replace community edition Docker images with enterprise edition images.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/use-meilisearch-ee

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

resources/docker/docker-compose.yaml (1)

10-10: Add :latest tag for consistency with other image references.

This file uses getmeili/meilisearch-enterprise without an explicit :latest tag, while other files in the PR (docker-compose.yaml, CONTRIBUTING.md, cypress.yml) explicitly use :latest. For consistency and clarity, add the tag.

-    image: getmeili/meilisearch-enterprise
+    image: getmeili/meilisearch-enterprise:latest

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f57f285 and 3a55606.

📒 Files selected for processing (5)

• .github/scripts/beta-docker-version.sh (1 hunks)
• .github/workflows/cypress.yml (1 hunks)
• CONTRIBUTING.md (1 hunks)
• docker-compose.yaml (1 hunks)
• resources/docker/docker-compose.yaml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)

• GitHub Check: Seer Code Review
• GitHub Check: playground-build (Node.js 20)
• GitHub Check: playground-build (Node.js 18)
• GitHub Check: cypress-run

🔇 Additional comments (4)

CONTRIBUTING.md (1)

51-52: Documentation updated consistently with image change.

The docker pull and run commands have been updated to reference the enterprise edition. This keeps the contributing guide aligned with the actual setup.

docker-compose.yaml (1)

20-20: Image reference updated correctly.

The meilisearch service image has been updated to the enterprise edition with the :latest tag, consistent with other configuration files in this PR.

.github/workflows/cypress.yml (1)

13-13: Image reference and quote normalization applied correctly.

The service image has been updated to the enterprise edition, and environment variables, ports, and node version have been normalized to double quotes for consistency with GitHub Actions conventions.

Please verify that the enterprise edition image is accessible and functions properly in the GitHub Actions CI environment. If the image has different authentication or network requirements, those should be configured in the workflow.

Also applies to: 15-16, 18-18, 26-26

.github/scripts/beta-docker-version.sh (1)

7-7: Docker Hub endpoint updated for enterprise image tag detection.

The script now queries the enterprise edition tags endpoint. The parsing logic remains unchanged, so this should work correctly as long as the enterprise edition publishes tags to the same Docker Hub endpoint with the same response format.

Verify that getmeili/meilisearch-enterprise/tags endpoint on Docker Hub is accessible and returns tags in the same format as the community edition. If the response format differs, the parsing logic may need adjustment.