Wanderer update breaks meilisearch

[rrole]

✅ Have you read and understood the above guidelines?

yes

🔎 Did you run the script with verbose mode enabled?

Yes, verbose mode was enabled and the output is included below

📜 What is the name of the script you are using?

Wanderer

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/wanderer.sh)"

⚙️ What settings are you using?

• Default Settings
• Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 13

📈 Which Proxmox version are you on?

pve-manager/9.0.11/3bf5476b8a4699e2

📝 Provide a clear and concise description of the issue.

After updating wanderer, the meilisearch instance reports an incompatible database. This prevents the service from starting.
To solve the issue, as per the meilisearch update gide , there are two options.
Option 1: Change the start command in /opt/wanderer/start.sh from
cd /opt/wanderer/source/search && meilisearch --master-key
to
cd /opt/wanderer/source/search && meilisearch --experimental-dumpless-upgrade --master-key
Then, restart the service. After the succesfull restart, change the command back to the original, do not restart the service again before the the database upgrade has completed (a restart is not needed and wanderer can be used normally).
Option 2: Import a dump. If a dump of your database has previously been created. The dump can be imported. Be aware that the database location has to be removed for this method to work, otherwise it will detect the previous database in this location and exit with an error.

🔄 Steps to reproduce the issue.

Update to a newer version of meilisearch

❌ Paste the full error output (if available).

Service output log after update:

ERROR meilisearch: error=Your database version (1.28.1) is incompatible with your current engine version (1.28.2).
To migrate data between Meilisearch versions, please follow our guide on https://www.meilisearch.com/docs/learn/update_and_migration/updating.

🖼️ Additional context (optional).

No response