<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Updating on Aroy Art</title><link>/tags/updating/</link><description>Recent post in Updating from Aroy Art</description><generator>Hugo -- gohugo.io</generator><language>en-gb</language><lastBuildDate>Wed, 07 Jan 2026 17:07:11 +0000</lastBuildDate><atom:link href="/tags/updating/index.xml" rel="self" type="application/rss+xml"/><item><title>Meilisearch Upgrades: The Docker Compose "One-Off" Method</title><link>/blog/2026-01-07-update-meilisearch-running-inside-of-docker-compose/</link><pubDate>Wed, 07 Jan 2026 17:07:11 +0000</pubDate><guid>/blog/2026-01-07-update-meilisearch-running-inside-of-docker-compose/</guid><description>&lt;h2 id="intro"&gt;Intro&lt;/h2&gt;
&lt;p&gt;Upgrading between major Meilisearch releases isn&amp;rsquo;t as simple as changing an image tag. Because Meilisearch uses a highly optimized internal database structure, its data files (&lt;code&gt;data.ms&lt;/code&gt;) are version-specific. If you try to point Meilisearch &lt;code&gt;v1.31&lt;/code&gt; at a &lt;code&gt;v1.12&lt;/code&gt; database, it will crash on startup.&lt;/p&gt;</description></item></channel></rss>