Meilisearch End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Meilisearch versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.0 | 1.0.2 | Feb 1, 2023 | Mar 30, 2023 | 1228 days past EOL | EOL |
| 1.1 | 1.1.1 | Mar 30, 2023 | May 30, 2023 | 1167 days past EOL | EOL |
| 1.2 | 1.2.1 | May 30, 2023 | Sep 13, 2023 | 1061 days past EOL | EOL |
| 1.3 | 1.3.5 | Jul 27, 2023 | Sep 20, 2023 | 1054 days past EOL | EOL |
| 1.4 | 1.4.2 | Sep 11, 2023 | Nov 13, 2023 | 1000 days past EOL | EOL |
| 1.5 | 1.5.1 | Nov 13, 2023 | Jan 15, 2024 | 937 days past EOL | EOL |
| 1.6 | 1.6.2 | Jan 15, 2024 | Mar 6, 2024 | 886 days past EOL | EOL |
| 1.7 | 1.7.6 | Mar 6, 2024 | May 2, 2024 | 829 days past EOL | EOL |
| 1.8 | 1.8.4 | May 2, 2024 | Jul 15, 2024 | 755 days past EOL | EOL |
| 1.9 | 1.9.1 | Jun 27, 2024 | Aug 27, 2024 | 712 days past EOL | EOL |
| 1.10 | 1.10.3 | Aug 21, 2024 | Oct 21, 2024 | 657 days past EOL | EOL |
| 1.11 | 1.11.3 | Oct 21, 2024 | Dec 23, 2024 | 594 days past EOL | EOL |
| 1.12 | 1.12.8 | Dec 23, 2024 | Feb 17, 2025 | 538 days past EOL | EOL |
| 1.13 | 1.13.3 | Feb 17, 2025 | Apr 14, 2025 | 482 days past EOL | EOL |
| 1.14 | 1.14.0 | Apr 14, 2025 | Jun 9, 2025 | 426 days past EOL | EOL |
| 1.15 | 1.15.2 | Jun 9, 2025 | Aug 4, 2025 | 370 days past EOL | EOL |
| 1.16 | 1.16.0 | Aug 4, 2025 | Aug 12, 2025 | 362 days past EOL | EOL |
| 1.17 | 1.17.1 | Aug 12, 2025 | Aug 18, 2025 | 356 days past EOL | EOL |
| 1.18 | 1.18.0 | Aug 18, 2025 | Aug 25, 2025 | 349 days past EOL | EOL |
| 1.19 | 1.19.1 | Aug 25, 2025 | Sep 8, 2025 | 335 days past EOL | EOL |
| 1.20 | 1.20.0 | Sep 8, 2025 | Sep 15, 2025 | 328 days past EOL | EOL |
| 1.21 | 1.21.0 | Sep 15, 2025 | Sep 24, 2025 | 319 days past EOL | EOL |
| 1.22 | 1.22.3 | Sep 24, 2025 | Oct 13, 2025 | 300 days past EOL | EOL |
| 1.23 | 1.23.0 | Oct 13, 2025 | Oct 20, 2025 | 293 days past EOL | EOL |
| 1.24 | 1.24.0 | Oct 20, 2025 | Nov 10, 2025 | 272 days past EOL | EOL |
| 1.25 | 1.25.0 | Nov 10, 2025 | Nov 17, 2025 | 265 days past EOL | EOL |
| 1.26 | 1.26.0 | Nov 17, 2025 | Nov 24, 2025 | 258 days past EOL | EOL |
| 1.27 | 1.27.0 | Nov 24, 2025 | Dec 1, 2025 | 251 days past EOL | EOL |
| 1.28 | 1.28.2 | Dec 1, 2025 | Dec 8, 2025 | 244 days past EOL | EOL |
| 1.29 | 1.29.0 | Dec 8, 2025 | Dec 15, 2025 | 237 days past EOL | EOL |
| 1.30 | 1.30.1 | Dec 15, 2025 | Dec 22, 2025 | 230 days past EOL | EOL |
| 1.31 | 1.31.0 | Dec 22, 2025 | Jan 12, 2026 | 209 days past EOL | EOL |
| 1.32 | 1.32.2 | Jan 12, 2026 | Jan 19, 2026 | 202 days past EOL | EOL |
| 1.33 | 1.33.1 | Jan 19, 2026 | Jan 26, 2026 | 195 days past EOL | EOL |
| 1.34 | 1.34.3 | Jan 26, 2026 | Feb 2, 2026 | 188 days past EOL | EOL |
| 1.35 | 1.35.1 | Feb 2, 2026 | Feb 23, 2026 | 167 days past EOL | EOL |
| 1.36 | 1.36.0 | Feb 23, 2026 | Mar 2, 2026 | 160 days past EOL | EOL |
| 1.37 | 1.37.0 | Mar 2, 2026 | Mar 9, 2026 | 153 days past EOL | EOL |
| 1.38 | 1.38.2 | Mar 9, 2026 | Mar 16, 2026 | 146 days past EOL | EOL |
| 1.39 | 1.39.0 | Mar 16, 2026 | Mar 23, 2026 | 139 days past EOL | EOL |
| 1.40 | 1.40.0 | Mar 23, 2026 | Mar 30, 2026 | 132 days past EOL | EOL |
| 1.41 | 1.41.0 | Mar 30, 2026 | Apr 13, 2026 | 118 days past EOL | EOL |
| 1.42 | 1.42.1 | Apr 13, 2026 | May 4, 2026 | 97 days past EOL | EOL |
| 1.43 | 1.43.1 | May 4, 2026 | May 18, 2026 | 83 days past EOL | EOL |
| 1.44 | 1.44.0 | May 18, 2026 | May 26, 2026 | 75 days past EOL | EOL |
| 1.45 | 1.45.2 | May 26, 2026 | Jun 8, 2026 | 62 days past EOL | EOL |
| 1.46 | 1.46.1 | Jun 8, 2026 | Jun 15, 2026 | 55 days past EOL | EOL |
| 1.47 | 1.47.1 | Jun 15, 2026 | Jun 24, 2026 | 46 days past EOL | EOL |
| 1.48 | 1.48.3 | Jun 22, 2026 | Jul 6, 2026 | 34 days past EOL | EOL |
| 1.49 | 1.49.0 | Jul 6, 2026 | Jul 20, 2026 | 20 days past EOL | EOL |
| 1.50 | 1.50.0 | Jul 20, 2026 | Jul 27, 2026 | 13 days past EOL | EOL |
| 1.51 | 1.51.0 | Jul 27, 2026 | Aug 3, 2026 | 6 days past EOL | EOL |
| 1.52 | 1.52.0 | Aug 3, 2026 | TBD | Supported | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/meilisearch)
What does Meilisearch end of life mean for your organization?
When a version of Meilisearch reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Meilisearch should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Your options when Meilisearch reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Meilisearch versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Meilisearch has 52 versions past end of life — security patches have stopped, but CVE disclosures haven't. The good news: extended support for Meilisearch exists — vetted vendors ship security patches for years past the official date. Tell us where to reach you and we'll reply with matched options and pricing guidance.