Changes related to Meilisearch v1.15.0

[Strift]

This issue lists the changes related to Meilisearch v1.15.0 that impact SDKs.

📅 Release date: 2025-06-09

Timelines & steps

Pre-release

• With the help of the changelog & this CI, define which integrations should be updated and how (New feature? Update README? Update tests?)
  • Fill in the "What to implement?" section below in this issue 👇. Minimal implementation: PHP, JS, meilisearch-js-plugins.
  • Open implementation issues in repositories that need implementation (if necessary for developers who will work on the tasks).
  • Discuss with the Product team if needed. At least share this issue to let them know about the decisions.
• Create a branch by running the pre-release script: only open branches for the integrations we choose to update (defined in the previous step) + Kubernetes repository + Cloud provider repository (changing the version)
• Update integrations according to the decisions (cf "What to implement?" section below in this issue 👇)
  ⚠️ If possible, this step is done before pre-release, once the feature is ready thanks to the prototype released by the engine team
  • JS
  • PHP
• Add code samples for the chosen up-to-date integrations with the new version of Meilisearch
• Create PRs to update the library version and prepare the changelogs
  • JS Update version for the next release (v0.51.0) meilisearch-js#1963
  • PHP Update version for the next release (v1.15.0) meilisearch-php#762
• Update Tier 2 SDKs so tests do not break when the engine adds new settings
  • Ruby Update settings tests to assert field inclusion in API responses meilisearch-ruby#634

Release day

• Merge PRs and publish the new SDK versions
  • JS @Strift
  • PHP @Strift
  • meilisearch-js-plugins (at least update meilisearch-js version) @Strift
• Merge Ruby PR (about tests) @Strift
• Merge the related PR in K8s repository @brunoocasali
• Publish DevOps tools @brunoocasali :
  • create the git tag
  • publish images (steps are in CONTRIBUTING.md)
• Remove useless AWS images (by using our internal script) @brunoocasali

Post-release

• Open issues in the repositories that are not up-to-date with the latest version of Meilisearch (including code samples) @Strift

Open issues for features that will not be implemented in the SDKs:

• Display the reason why the batcher stopped batching tasks meilisearch#5511 (All SDKs except Python and Ruby)
• Detect and disallow typos for high-entropy words meilisearch#5344 (All SDKs except JavaScript and PHP)

What to implement?

Detect and disallow typos for high-entropy words

Additional context

• Engine issue: Detect and disallow typos for high-entropy words meilisearch#5344
• Usage guide: https://meilisearch.notion.site/Deactivate-typo-tolerance-on-specific-kinds-of-terms-1a44b06b651f809d9cb7db67b322a4b8

TODO:

• JS: Add disableOnNumbers to typo tolerance settings meilisearch-js#1951
• PHP: Add disableOnNumbers field to typo tolerance settings meilisearch-php#753

Allow lexicographic filtering of strings

Additional context

• Engine issue: Allow comparison operators for strings in filters meilisearch#5554
• Usage guide: directly in the issue

TODO:

• JS: No changes required
• PHP: No changes required