β οΈ Breaking Change
Impact Score: 7/10
Meilisearch: v1.25.0 πββ¬
Source available β automated, not human-reviewed
Component: meilisearch Β· Channel: stable. Automated analysis, not a compatibility certification. How this works.
Analysis updated: 2026-11-01.
Breaking-change evidence from the source
β οΈ [Breaking - Security] Redact Authorization header in webhooks by @dureuill in #5968
- Technically a **breaking change**, as users could previously get the key value back when getting the webhook, and that will no longer be possible
β‘ Executive Summary (TL;DR)
Meilisearch v1.25.0. Source highlight: π¬ [Experimental]: Search personalization by @ManyTheFish in #5775
Who Does This Impact? (Role-Based Analysis)
π» Software Engineers & Devs
Check the source notes against the package and APIs you use before upgrading.
π Product & Engineering Leads
Use the documented changes to assess relevance to your product; release frequency alone is not a quality measure.
βοΈ DevOps & Security
Verify the target version, runtime requirements and rollback procedure in the official documentation.
β οΈ Breaking Changes & Deprecations (2)
- β οΈ [Breaking - Security] Redact Authorization header in webhooks by @dureuill in #5968
- - Technically a **breaking change**, as users could previously get the key value back when getting the webhook, and that will no longer be possible
β¨ New Features & Capabilities (1)
- Add Flickr example to README
π View Raw Release Notes (Original Developer Log)
## β¨ Enhancement
### π¬ [Experimental]: Search personalization by @ManyTheFish in #5775
Add the ability to dynamically rerank the search results based on Cohere using a personalized prompt.
For more information on how to set it up, see the dedicated [experimental feature discussion](https://github.com/orgs/meilisearch/discussions/866).
### π¬ [Experimental]: Upload snapshot tarballs to S3 by @Kerollmops in #5948
Add the ability to upload snapshots directly to S3. It has many advantages, such as being able to stream the entire process and effectively utilizing multipart technology to send chunks of data in parallel.
For more information on how to use it, see the dedicated [experimental feature discussion](https://github.com/orgs/meilisearch/discussions/869).
## πͺ²Β Bug fixes
### β οΈ [Breaking - Security] Redact Authorization header in webhooks by @dureuill in #5968
The value of the `Authorization` header is now redacted when getting webhook, getting webhooks, or in the object returned when posting a new webhook or deleting a webhook.
- Impact on Cloud: Similarly to embedder API, the UI should make sure to never send the `Authorization` header back after it has been redacted
- Technically a **breaking change**, as users could previously get the key value back when getting the webhook, and that will no longer be possible
### π° Fix the LMDB fork memory leak by @Kerollmops in #5967
This bug was causing crashes in the recent indexer optimizations. If you deactivated these optimizations by setting the following environment variables:
```
MEILI_EXPERIMENTAL_NO_EDITION_2024_FOR_PREFIX_POST_PROCESSING=true
MEILI_EXPERIMENTAL_NO_EDITION_2024_FOR_FACET_POST_PROCESSING=true
```
You can now safely reactivate them without experiencing memory leaks.
### π©πͺ Hotfix German word segmentation by @ManyTheFish in https://github.com/meilisearch/charabia/pull/360
German word segmentation relies on a word dictionary to segment words, but if a word is not part of the dictionary, it is cut into bigrams. The segmenter will now skip segmenting unknown words:
```yaml
Source: "Feuchteschutz"
Before: ["Fe" "uc" "ht" "es, "ch", "utz"]
After: ["Feuchteschutz"]
Source: "insgesamt"
Before: ["in" "sg" "es" "amt"]
After: ["insgesamt"]
```
> If you have a Meilisearch database containing German words, you must reindex your data manually.
### π¨π³ Prevent splitting of numbers and English words in Chinese text segmentation by @JinheLin in https://github.com/meilisearch/charabia/pull/354
Itβs very common for Chinese, numbers, and English to appear together in the same sentence.
We now ensure that numbers and English are not segmented differently between segmenters:
```yaml
Source: "ζδ»2025εΉ΄εΌε§ε¦δΉ Rustθ―θ¨γ"
Before: ["ζ", "δ»", "2", "0", "2", "5", "εΉ΄", "εΌε§", "ε¦δΉ ", "R", "u", "s", "t", "θ―θ¨", "γ"]
After: ["ζ", "δ»", "2025", "εΉ΄", "εΌε§", "ε¦δΉ ", "Rust", "θ―θ¨", "γ"]
```
> If you have a Meilisearch database containing Chinese words, you must reindex your data manually.
## π© Miscellaneous
- Add Flickr example to README by @Kerollmops in https://github.com/meilisearch/meilisearch/pull/5961
Thanks to @JinheLin, @dureuill, @Kerollmops, and @ManyTheFish for their contribution! π