Mealie 3.31.0 upgrade: security fixes and new upload limit
Summary
Mealie 3.31.0 is a large release. The maintainers say it fixes a batch of security issues and recommend that everyone update. Details are promised in advisories “shortly after the release”. The fixes cover access between groups and households, private recipe visibility on public pages, password reset links and oversized uploads.
New features include PDF export for recipes and cookbooks, a days view in the meal planner, and cleaner AI recipe imports. Large recipe lists and the timeline should be faster.
Breaking changes and deprecations
From the release notes (reported, not all tested by us):
- Request bodies are capped by
MAX_UPLOAD_SIZE_MB(default1024). Larger uploads, such as big migrations or backups, get a 413 until you raise it. - Password reset links expire after
PASSWORD_RESET_TOKEN_TIMEhours (default1). - New
APPRISE_ALLOWED_SCHEMASsetting limits which notification services notifiers can use. - The recipe API no longer returns
cookTime. The upgrade moves existing values intoperformTime, which the UI shows as “Cook Time”. Older clients can still sendcookTime.
Tested in our lab
We installed 3.30.0 with the documented Docker Compose (SQLite) setup, created a recipe with a cook time through the API, then stopped the container with docker compose down, changed the image tag to v3.31.0, pulled and started it.
- The upgrade worked. The container came up healthy, the version endpoint reported
v3.31.0, and the web UI answered with HTTP 200. - Data survived. The recipe was still there after the upgrade.
- The
cookTimechange is real. Before the upgrade the recipe had"cookTime":"25 minutes"and"performTime":null. After it,"performTime":"25 minutes"and nocookTimefield. If you have scripts that readcookTimefrom the API, update them. - The log showed a database migration running at startup. We found no errors or tracebacks. The only lines matching “error” were theme colour settings.
Not tested: PDF export, the days view, AI import, the upload limit, password reset expiry, Apprise settings, PostgreSQL setups, and the security fixes themselves.
Lab log
$ curl -s localhost:9925/api/app/about
{"production":true,"version":"v3.30.0",[...]
$ curl -s localhost:9925/api/recipes/lab-soup -H "Authorization: Bearer [redacted]" | grep -o "\"\(cookTime\|performTime\|prepTime\)\":[^,]*"
"prepTime":"10 minutes"
"cookTime":"25 minutes"
"performTime":null
$ docker compose down
[...]
Container mealie Removed
$ docker compose pull
[...]
mealie Pulled
$ docker compose up -d
Container mealie Created
Container mealie Starting
Container mealie Started
$ curl -s localhost:9925/api/app/about
{"production":true,"version":"v3.31.0",[...]
$ curl -s localhost:9925/api/recipes/lab-soup -H "Authorization: Bearer [redacted]" | grep -o "\"\(name\|cookTime\|performTime\|prepTime\)\":[^,]*"
"name":"Lab Soup"
"prepTime":"10 minutes"
"performTime":"25 minutes"
$ curl -s -o /dev/null -w "%{http_code}\n" localhost:9925/
200
$ docker ps --format "{{.Names}} {{.Status}}"
mealie Up 51 seconds (healthy)
Reported by others
Nothing beyond the release notes. The maintainers say security advisories will follow. We did not check for them.
Verdict
Upgrade now. The release carries security fixes, and our upgrade from 3.30.0 was clean. Before you upgrade, back up your data. If you import large archives or backups, raise MAX_UPLOAD_SIZE_MB. Also update any API scripts that rely on cookTime.
sources
other Mealie releases
- 3.30.0 upgrade now