Upgrade lasuite-meet from 0.4.0+v1.19.0 to 0.4.1+v1.19.0.
Infrastructure image bumps only — the primary Meet app stays at v1.19.0.
Image tag changes
Service
Old tag
New tag
livekit (livekit/livekit-server)
v1.12.0
v1.13.1
redis
8.6.4
8.8.0
Operator action required
LiveKit v1.13.1: Removes backwards compatibility for TURN auth without TTL (deprecated since v1.12.0). If you never set LIVEKIT_FORCE_TCP and use the default TURN config, no action needed. If you have a custom TURN setup without TTL configured, set the TTL before deploying.
Redis 8.8.0: Drop-in upgrade. No config changes required.
Verified on cc-ci
Direct chaos-deploy to dev-lasuite-meet.ci.commoninternet.net: redis 8.8.0 and livekit v1.13.1 both started cleanly, all services converged 1/1, migrations ran successfully.
Tested green on the cc-ci recipe CI server (full suite, cold, against this PR head). NOT merged — for operator review.
Upgrade `lasuite-meet` from `0.4.0+v1.19.0` to `0.4.1+v1.19.0`.
Infrastructure image bumps only — the primary Meet app stays at v1.19.0.
## Image tag changes
| Service | Old tag | New tag |
|---------|---------|---------|
| livekit (livekit/livekit-server) | v1.12.0 | v1.13.1 |
| redis | 8.6.4 | 8.8.0 |
## Operator action required
**LiveKit v1.13.1**: Removes backwards compatibility for TURN auth without TTL (deprecated since v1.12.0). If you never set `LIVEKIT_FORCE_TCP` and use the default TURN config, no action needed. If you have a custom TURN setup without TTL configured, set the TTL before deploying.
**Redis 8.8.0**: Drop-in upgrade. No config changes required.
## Verified on cc-ci
Direct chaos-deploy to `dev-lasuite-meet.ci.commoninternet.net`: redis 8.8.0 and livekit v1.13.1 both started cleanly, all services converged 1/1, migrations ran successfully.
Tested green on the cc-ci recipe CI server (full suite, cold, against this PR head). NOT merged — for operator review.
cc @trav @notplants
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Upgrade
lasuite-meetfrom0.4.0+v1.19.0to0.4.1+v1.19.0.Infrastructure image bumps only — the primary Meet app stays at v1.19.0.
Image tag changes
Operator action required
LiveKit v1.13.1: Removes backwards compatibility for TURN auth without TTL (deprecated since v1.12.0). If you never set
LIVEKIT_FORCE_TCPand use the default TURN config, no action needed. If you have a custom TURN setup without TTL configured, set the TTL before deploying.Redis 8.8.0: Drop-in upgrade. No config changes required.
Verified on cc-ci
Direct chaos-deploy to
dev-lasuite-meet.ci.commoninternet.net: redis 8.8.0 and livekit v1.13.1 both started cleanly, all services converged 1/1, migrations ran successfully.Tested green on the cc-ci recipe CI server (full suite, cold, against this PR head). NOT merged — for operator review.
cc @trav @notplants
!testme
🌻 cc-ci —
lasuite-meet@05cdafb5✅ passedfull logs · dashboard
Pull request closed