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

chore: upgrade to 0.4.2+v1.21.0 #7

Open
autonomic-bot wants to merge 1 commits from upgrade-0.4.2+v1.21.0 into main
pull from: upgrade-0.4.2+v1.21.0
merge into: recipe-maintainers:main
Conversation 2 Commits 1 Files Changed 1 +4 -4
autonomic-bot commented 2026-06-16 23:13:18 +00:00
Owner
Copy Link

Upgrade lasuite-meet from 0.4.1+v1.19.0 to 0.4.2+v1.21.0.

Patch recipe bump (no operator action required): image versions increase but
deploying "just works" — no new env vars, secrets, or DB migrations. v1.20.0 and
v1.21.0 are bug-fix / UX / audio improvements only.

Image tag changes

Service Old tag New tag
app (lasuite/meet-frontend) v1.19.0 v1.21.0
backend (lasuite/meet-backend) v1.19.0 v1.21.0
celery (lasuite/meet-backend) v1.19.0 v1.21.0

Release notes: https://github.com/suitenumerique/meet/releases/tag/v1.21.0 ,
https://github.com/suitenumerique/meet/releases/tag/v1.20.0

Deploy

Deployed to the test instance; all 7 services converged healthy on v1.21.0
(app, backend, celery, db, redis, web healthy; livekit up — no healthcheck by design).

Test results

Test Result
tests/health_check.py (HTTPS 200) PASS
tests/oidc_login.py Step 1 (Meet -> Keycloak redirect) PASS
tests/webrtc-media.py Step 1 (HTTPS, WSS signaling, TCP 7881, UDP 7882, TURN/UDP 443) PASS
tests/oidc_login.py Step 2-3, tests/meeting_flow.py, tests/webrtc-media.py Step 2 BLOCKED — Keycloak not deployed on test server (realm 404); pre-existing environment outage, not an upgrade regression

All non-Keycloak test steps pass, including the full WebRTC media/TURN stack and
Meet's own OIDC redirect configuration. The blocked steps depend on the external
Keycloak instance, which is currently not deployed on the test server.

cc @trav @notplants

Upgrade `lasuite-meet` from `0.4.1+v1.19.0` to `0.4.2+v1.21.0`. Patch recipe bump (no operator action required): image versions increase but deploying "just works" — no new env vars, secrets, or DB migrations. v1.20.0 and v1.21.0 are bug-fix / UX / audio improvements only. ## Image tag changes | Service | Old tag | New tag | |---------|---------|---------| | app (`lasuite/meet-frontend`) | v1.19.0 | v1.21.0 | | backend (`lasuite/meet-backend`) | v1.19.0 | v1.21.0 | | celery (`lasuite/meet-backend`) | v1.19.0 | v1.21.0 | Release notes: https://github.com/suitenumerique/meet/releases/tag/v1.21.0 , https://github.com/suitenumerique/meet/releases/tag/v1.20.0 ## Deploy Deployed to the test instance; all 7 services converged healthy on v1.21.0 (app, backend, celery, db, redis, web healthy; livekit up — no healthcheck by design). ## Test results | Test | Result | |------|--------| | `tests/health_check.py` (HTTPS 200) | PASS | | `tests/oidc_login.py` Step 1 (Meet -> Keycloak redirect) | PASS | | `tests/webrtc-media.py` Step 1 (HTTPS, WSS signaling, TCP 7881, UDP 7882, TURN/UDP 443) | PASS | | `tests/oidc_login.py` Step 2-3, `tests/meeting_flow.py`, `tests/webrtc-media.py` Step 2 | BLOCKED — Keycloak not deployed on test server (realm 404); pre-existing environment outage, not an upgrade regression | All non-Keycloak test steps pass, including the full WebRTC media/TURN stack and Meet's own OIDC redirect configuration. The blocked steps depend on the external Keycloak instance, which is currently not deployed on the test server. cc @trav @notplants
autonomic-bot added 1 commit 2026-06-16 23:13:18 +00:00
chore: upgrade to 0.4.2+v1.21.0
All checks were successful
cc-ci/testme cc-ci: success
Details
97684f9de9
autonomic-bot requested review from trav 2026-06-16 23:13:19 +00:00
autonomic-bot requested review from notplants 2026-06-16 23:13:19 +00:00
autonomic-bot commented 2026-06-17 02:03:01 +00:00
Author
Owner
Copy Link

!testme

!testme
autonomic-bot commented 2026-06-17 02:03:23 +00:00
Author
Owner
Copy Link

🌻 cc-ci — lasuite-meet @ 97684f9d ✅ passed

cc-ci result card

level

full logs · dashboard

<!-- cc-ci:testme --> 🌻 **cc-ci** — `lasuite-meet` @ `97684f9d` ✅ **passed** [![cc-ci result card](https://ci.commoninternet.net/runs/730/summary.png)](https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/730) [![level](https://ci.commoninternet.net/runs/730/badge.svg)](https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/730) [full logs](https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/730) · [dashboard](https://ci.commoninternet.net/)
All checks were successful
cc-ci/testme cc-ci: success
Details
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin upgrade-0.4.2+v1.21.0:upgrade-0.4.2+v1.21.0
git checkout upgrade-0.4.2+v1.21.0
Sign in to join this conversation.
Reviewers
No Reviewers
trav
notplants
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#7
No description provided.
Delete Branch "upgrade-0.4.2+v1.21.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?