Changes related to the next Meilisearch release (v1.16.0)

[meili-bot]

This PR gathers the changes related to the next Meilisearch release (v1.16.0) so that this package is ready when the official release is out.

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

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

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

Summary by CodeRabbit

• Chores
  • Updated the default Meilisearch version to v1.16.0.

[coderabbitai]

Walkthrough

The default value for the meilisearch_version variable in the meilisearch.pkr.hcl file was updated from "v1.15.0" to "v1.16.0". No other changes were made.

Changes

Cohort / File(s)	Change Summary
Meilisearch Version Update meilisearch.pkr.hcl	Updated the default value of meilisearch_version from "v1.15.0" to "v1.16.0".

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A hop, a skip, a version leap,
From fifteen to sixteen, changes neat.
The carrots cheer, the code is bright,
With every patch, the future’s light.
Meilisearch grows, the garden thrives,
Onward, upward, in our hutchy lives! 🥕

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9d1db21 and 5d60a1d.

📒 Files selected for processing (1)

• meilisearch.pkr.hcl (1 hunks)

🔇 Additional comments (2)

meilisearch.pkr.hcl (2)

7-10: Version bump looks good but remember the release/blocking constraint

Changing the default to v1.16.0 is the only diff and is correct for preparing the next image build.
No functional or syntax issues introduced here.

---

7-10: Double-check downstream install scripts before merging

scripts/meilisearch-install.sh (invoked later in the build) fetches the binary using MEILISEARCH_VERSION. If the official GitHub release/tag v1.16.0 is not yet published, packer builds will fail at provisioning time.
Please verify that:

1. The script gracefully handles “404 Not Found” (e.g., retries or emits a clear error).
2. CI / nightly image jobs are gated so they don’t start until the tag is live.

Optionally, add a quick pre-flight check in the install script:

-# existing fetch logic …
+if ! curl -s --head --fail "https://github.com/meilisearch/meilisearch/releases/download/${MEILISEARCH_VERSION}/meilisearch-linux-amd64" >/dev/null; then
+  echo "Meilisearch ${MEILISEARCH_VERSION} is not yet available. Abort." >&2
+  exit 1
+fi

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch bump-meilisearch-v1.16.0

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.