Replaces #3, which had drifted out of sync with upstream main (it re-introduced renovate.json, README docs, and the .env.sample TURN fix that are already merged upstream). This PR branches directly off current upstream main so the diff contains only the version bump.
Upgrade lasuite-meet to `0.4.0+v1.19.0`.
Single commit, only `compose.yml`:
- meet-frontend / meet-backend / celery: `v1.16.0` → `v1.19.0`
- redis: `8.6.3` → `8.6.4`
- version label: `0.3.0+v1.16.0` → `0.4.0+v1.19.0`
Replaces #3, which had drifted out of sync with upstream main (it re-introduced `renovate.json`, README docs, and the `.env.sample` TURN fix that are already merged upstream). This PR branches directly off current upstream main so the diff contains only the version bump.
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-meet to
0.4.0+v1.19.0.Single commit, only
compose.yml:v1.16.0→v1.19.08.6.3→8.6.40.3.0+v1.16.0→0.4.0+v1.19.0Replaces #3, which had drifted out of sync with upstream main (it re-introduced
renovate.json, README docs, and the.env.sampleTURN fix that are already merged upstream). This PR branches directly off current upstream main so the diff contains only the version bump.cc @trav @notplants
!testme
🌻 cc-ci —
lasuite-meet@e8776e96✅ passedfull logs · dashboard
Auto-closed by /recipe-upgrade: its changes are already in upstream main (merged upstream); mirror main re-synced
Pull request closed