chore(deps): update ghcr.io/mealie-recipes/mealie docker tag to v3.22.0

[bde-dev]

This PR contains the following updates:

Package	Update	Change
ghcr.io/mealie-recipes/mealie	minor	v3.21.0 → v3.22.0

---

Release Notes

mealie-recipes/mealie (ghcr.io/mealie-recipes/mealie)

v3.22.0

Compare Source

🍴🍴🍴🍴🍴🍴

The previous version of Mealie (v3.21.0) introduced a ⚠️BREAKING CHANGE⚠️ for instances using OIDC: Mealie now requires your OIDC provider to confirm the user's email address before allowing the login. This prevents an unverified, self-asserted email address from being used to match (and sign in) to an existing Mealie account.

If an identity provider does not emit the email_verified claim, logins now fail. If you cannot configure your identity provider to include the email_verified claim, you can set OIDC_REQUIRES_EMAIL_VERIFICATION to false (this is not recommended per the above security concerns). See the docs for more details.

🎉 Highlights

New to this release, many improvements have been made to make importing recipes more reliable. Mealie does a better job of looking like a real browser, rotates between several browser signatures, and retries more intelligently when a site pushes back. This works out of the box, with no configuration.

For sites sitting behind extra bot protection (such as Cloudflare) server admins have two additional controls:

• Proxy support, which routes recipe and image requests through a proxy. This helps with sites that block your server's IP address.
• FlareSolverr support, which hands the page to a real headless browser as a last resort. This helps with challenges that Mealie can't get past on its own.

Both require additional configuration to work. Mealie does not ship or manage either one. You supply the proxy, and host FlareSolverr yourself (it runs nicely as a sidecar container). See the configuration docs for the settings, setup details, and an example compose file.

✨ New features

• feat: Improve scraper resiliency and add both proxy and FlareSolverr support @​michael-genson (#​7953)
• feat: Add feedback for bad JSON in HTML-JSON page @​michael-genson (#​7956)
• feat: Announce OIDC email change and announce new scraper capabilities @​michael-genson (#​7963)

🐛 Bug fixes

• fix: Clear InputLabelType item-id as null instead of empty string @​lehnerpat (#​7950)

🧰 Maintenance

5 changes

• chore(l10n): New Crowdin updates @​hay-kot (#​7943)
• chore(l10n): New Crowdin updates @​hay-kot (#​7945)
• chore(l10n): Crowdin locale sync @​mealie-actions[bot] (#​7948)
• chore(l10n): New Crowdin updates @​hay-kot (#​7952)
• chore(l10n): New Crowdin updates @​hay-kot (#​7960)

🔨 Internal development

• dev: Update front end unit test dependencies @​miah120 (#​7949)

⬆️ Dependency updates

5 changes

• chore(deps): update dependency js-yaml to v5.2.2 [security] @​renovate[bot] (#​7951)
• chore(deps): update dependency pre-commit to v4.6.1 @​renovate[bot] (#​7955)
• chore(deps): lock file maintenance @​renovate[bot] (#​7958)
• fix(deps): update dependency pillow-heif to v1.5.0 @​renovate[bot] (#​7959)
• fix(deps): update dependency openai to v2.47.0 @​renovate[bot] (#​7962)

🍴🍴🍴🍴🍴🍴

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate.

[bde-dev]

AI Assessment

Field	Value
Decision	NEEDS_REVIEW
Risk Level	MEDIUM
Update Type	MINOR
Component	ghcr.io/mealie-recipes/mealie
Version	v3.21.0 -> v3.22.0
Breaking Changes	true

Analysis

While v3.22.0 itself is a stable minor update with improvements and bug fixes, it builds upon v3.21.0 which introduced a breaking change for OIDC authentication. The homelab maintainer needs to verify: (1) whether OIDC is being used, (2) whether their identity provider emits email_verified claim, and (3) if not, whether they need to set the override environment variable. This is medium risk due to the pre-existing breaking change interaction, but the application is non-critical infrastructure.

Recommendation

NEEDS_REVIEW: Before merging, verify your OIDC configuration (if used). If you use OIDC authentication, confirm your identity provider emits the 'email_verified' claim, or ensure the OIDC_REQUIRES_EMAIL_VERIFICATION environment variable is set to 'false' in your deployment. If you don't use OIDC, this update is safe to apply as it includes improvements to recipe scraping and bug fixes.

---

Analyzed by n8n AI Agent using Claude