Mealie 3.30.0 upgrade: no breaking changes, one env var removed

released
lab run
upgraded from
3.29.0
guest
Ubuntu 26.04 VM
tested
yes, in our lab

Summary

Mealie 3.30.0 is a large feature release with several security and permission fixes. Highlights from the release notes:

  • AI prompts can now be customised inside the app. You can append to a prompt, replace it, or add global instructions.
  • Each recipe instruction step can have its own duration.
  • Meal plan entries can be set for a whole week instead of a single day.
  • Recipes can be sorted by total time, and the recipe owner is shown.
  • New OIDC_VERIFY_X509_STRICT setting.
  • Mealie now listens on IPv4 and IPv6 by default.

Breaking changes and deprecations

Reported by the release notes:

  • The OPENAI_CUSTOM_PROMPT_DIR environment variable has been removed. The notes say existing custom prompts are imported into the new in-app format automatically.
  • An unrecognised DB_ENGINE value is now rejected instead of silently falling back to SQLite (#8605).
  • Managing units, tools, labels and recipe actions now needs the can_organize permission. Managing notifiers and webhooks now needs can_manage_household. Users who relied on looser access may see permission errors.

We did not test any of these. Our test used none of these settings.

Tested in our lab

Tested in our lab: a Docker Compose install on SQLite, upgraded from 3.29.0 to 3.30.0.

  • 3.29.0 started healthy and answered on its API. We created one recipe (“Pumpkin Soup”).
  • We stopped the stack with docker compose down, changed the image tag, pulled and started again.
  • 3.30.0 came up healthy, reported the new version, and the recipe was still listed.
  • The log showed “Migration needed. Performing migration…” on first start, with no errors in our log search.
  • The web UI returned HTTP 200, and the API also answered over IPv6 ([::1]).

We did not test AI prompts, OIDC, PostgreSQL, meal plans, instruction durations or the permission changes. We tested with a single admin user and one recipe, so this is a small data set.

Lab log

$ docker compose up -d
 Container mealie  Started
$ curl -s localhost:9925/api/app/about
{"production":true,"version":"v3.29.0","demoStatus":false,[...]
$ docker compose down
 Network mealie_default  Removed
$ docker compose pull
 mealie Pulled
$ docker compose up -d
 Container mealie  Started
$ docker compose ps
NAME      IMAGE                                   COMMAND         SERVICE   CREATED          STATUS                    PORTS
mealie    ghcr.io/mealie-recipes/mealie:v3.30.0   "/app/run.sh"   mealie    46 seconds ago   Up 44 seconds (healthy)   0.0.0.0:9925->9000/tcp, [::]:9925->9000/tcp
$ curl -s localhost:9925/api/app/about | head -c 60
{"production":true,"version":"v3.30.0","demoStatus":false,"a
$ curl -s localhost:9925/api/recipes -H "Authorization: Bearer [redacted]" | head -c 120
{"page":1,"per_page":50,"total":1,"total_pages":1,"items":[{"id":"fd82cf34-c263-4fe0-838c-18974ebb1327","userId":"d19fcb
$ curl -s -o /dev/null -w "%{http_code}\n" localhost:9925/
200
$ curl -s -g "http://[::1]:9925/api/app/about" | head -c 40
{"production":true,"version":"v3.30.0","

Reported by others

We did not look for user reports for this release. The only source is the official release notes.

Verdict

Upgrade when convenient. In our small SQLite test the upgrade was uneventful and data survived. Before upgrading, check whether you set OPENAI_CUSTOM_PROMPT_DIR or rely on non-organizer users managing units, labels or webhooks. Back up your data volume first, as always.

sources

other Mealie releases