recipe-maintainers/lasuite-meet
0
0
Fork 0
Code Issues Pull Requests 2 Actions Packages Projects Releases Wiki Activity

chore: upgrade to 0.3.0+v1.16.0 #1

Closed
autonomic-bot wants to merge 0 commits from upgrade-0.3.0+v1.16.0 into main
pull from: upgrade-0.3.0+v1.16.0
merge into: recipe-maintainers:main
Conversation 1 Commits - Files Changed - +6 -6
autonomic-bot commented 2026-05-25 19:17:12 +00:00
Owner
Copy Link

Upgrade lasuite-meet from 0.2.0+v1.15.0 to 0.3.0+v1.16.0.

Image tag changes

Service Old tag New tag
app (lasuite/meet-frontend) v1.15.0 v1.16.0
backend (lasuite/meet-backend) v1.15.0 v1.16.0
celery (lasuite/meet-backend) v1.15.0 v1.16.0
livekit (livekit/livekit-server) v1.11.0 v1.12.0
web (nginx) 1.29.8 1.31.1

Release notes

Test results (test instance: lasuite-meet.cctest.autonomic.zone)

Test Result
tests/health_check.py PASS
tests/oidc_login.py PASS
tests/meeting_flow.py PASS
tests/webrtc-media.py PASS (end-to-end WebRTC: signaling, ICE, TURN relay, audio)
URL https://lasuite-meet.cctest.autonomic.zone PASS (HTTP 200)
WSS wss://livekit-meet.cctest.autonomic.zone signaling PASS

All 7 services deployed healthy. No operator action required for this upgrade (Django migrations run automatically via AUTO_MIGRATIONS=true).

Next steps (after PR review)

# 1. Review the PR on git.autonomic.zone (link above)
# 2. Pull the PR branch locally:
cd ~/.abra/recipes/lasuite-meet
git fetch git@git.autonomic.zone:recipe-maintainers/lasuite-meet.git upgrade-0.3.0+v1.16.0:upgrade-0.3.0+v1.16.0
git checkout upgrade-0.3.0+v1.16.0
# 3. Push to your upstream fork:
git push dev HEAD:upgrade-0.3.0+v1.16.0
# 4. Open & merge a PR on upstream:
#    https://git.coopcloud.tech/coop-cloud/lasuite-meet/pulls
# 5. After upstream merges, push the tag to publish:
git push dev 0.3.0+v1.16.0

cc @trav @notplants

Upgrade `lasuite-meet` from `0.2.0+v1.15.0` to `0.3.0+v1.16.0`. ## Image tag changes | Service | Old tag | New tag | |---------|---------|---------| | app (lasuite/meet-frontend) | v1.15.0 | v1.16.0 | | backend (lasuite/meet-backend) | v1.15.0 | v1.16.0 | | celery (lasuite/meet-backend) | v1.15.0 | v1.16.0 | | livekit (livekit/livekit-server) | v1.11.0 | v1.12.0 | | web (nginx) | 1.29.8 | 1.31.1 | ## Release notes - Meet v1.16.0: https://github.com/suitenumerique/meet/releases/tag/v1.16.0 (no breaking changes for compose deployments) - LiveKit v1.12.0: https://github.com/livekit/livekit/releases/tag/v1.12.0 (TURN security changes backwards-compatible this release; new behaviour removal planned in a future release) - nginx 1.31.1: routine stable bump for the static frontend sidecar ## Test results (test instance: lasuite-meet.cctest.autonomic.zone) | Test | Result | |------|--------| | `tests/health_check.py` | PASS | | `tests/oidc_login.py` | PASS | | `tests/meeting_flow.py` | PASS | | `tests/webrtc-media.py` | PASS (end-to-end WebRTC: signaling, ICE, TURN relay, audio) | | URL `https://lasuite-meet.cctest.autonomic.zone` | PASS (HTTP 200) | | WSS `wss://livekit-meet.cctest.autonomic.zone` signaling | PASS | All 7 services deployed healthy. No operator action required for this upgrade (Django migrations run automatically via AUTO_MIGRATIONS=true). ## Next steps (after PR review) ```bash # 1. Review the PR on git.autonomic.zone (link above) # 2. Pull the PR branch locally: cd ~/.abra/recipes/lasuite-meet git fetch git@git.autonomic.zone:recipe-maintainers/lasuite-meet.git upgrade-0.3.0+v1.16.0:upgrade-0.3.0+v1.16.0 git checkout upgrade-0.3.0+v1.16.0 # 3. Push to your upstream fork: git push dev HEAD:upgrade-0.3.0+v1.16.0 # 4. Open & merge a PR on upstream: # https://git.coopcloud.tech/coop-cloud/lasuite-meet/pulls # 5. After upstream merges, push the tag to publish: git push dev 0.3.0+v1.16.0 ``` cc @trav @notplants
autonomic-bot added 1 commit 2026-05-25 19:17:12 +00:00
chore: upgrade to 0.3.0+v1.16.0 3caa6bcde7
autonomic-bot requested review from trav 2026-05-25 19:17:12 +00:00
autonomic-bot requested review from notplants 2026-05-25 19:17:12 +00:00
autonomic-bot commented 2026-06-01 08:38:48 +00:00
Author
Owner
Copy Link

Auto-closed by /recipe-upgrade: its changes are already in upstream main (merged upstream); mirror main re-synced

Auto-closed by /recipe-upgrade: its changes are already in upstream main (merged upstream); mirror main re-synced
autonomic-bot closed this pull request 2026-06-01 08:38:48 +00:00

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No Reviewers
notplants
trav
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
autonomic autonomic-bot notplants trav
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: recipe-maintainers/lasuite-meet#1
No description provided.
Delete Branch "upgrade-0.3.0+v1.16.0"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?