Upstream sources — lasuite-meet

service	image	source repo	releases / changelog
app	lasuite/meet-frontend	https://github.com/suitenumerique/meet	https://github.com/suitenumerique/meet/releases
backend	lasuite/meet-backend	https://github.com/suitenumerique/meet	https://github.com/suitenumerique/meet/releases
celery	lasuite/meet-backend	https://github.com/suitenumerique/meet	https://github.com/suitenumerique/meet/releases
db	pgautoupgrade/pgautoupgrade	https://github.com/pgautoupgrade/pgautoupgrade	https://github.com/pgautoupgrade/pgautoupgrade/releases
redis	redis	https://github.com/redis/redis	https://hub.docker.com/_/redis/tags
livekit	livekit/livekit-server	https://github.com/livekit/livekit	https://github.com/livekit/livekit/releases
web	nginx	https://github.com/nginx/nginx	https://nginx.org/en/CHANGES

Standing notes

meet-frontend, meet-backend (used for both backend + celery services) share the same version tag from the suitenumerique/meet monorepo. Upgrade app, backend, and celery in lockstep.
AUTO_MIGRATIONS=true means DB migrations run automatically on backend startup. No manual step needed.
v1.17.0–v1.19.0: no breaking changes documented; feature additions only (participant muting, PiP, S3 recording, API exposure). Standard rolling upgrade applies.
v1.19.0: security fix for CVE-2026-45409 (idna ≥3.15) — no operator action needed (baked into image).
Recipe version label convention: 0.X.Y+vA.B.C where A.B.C is the meet version.
LiveKit version is decoupled from meet version; only bump if explicitly required.
v1.13.1: removes backwards compatibility for TURN auth without TTL (deprecated in v1.12.0). Operators who never set TURN TTL must add it before upgrading LiveKit to v1.13.x. No new required env vars for standard deployments.
Redis 8.8.0: compatible drop-in upgrade; includes ReJSON module with V5–V7 API exported. No config or persistence-format changes.