chore: upgrade to 0.4.0+v1.19.0 #3
Reference in New Issue
Block a user
No description provided.
Delete Branch "upgrade-0.3.0+v1.17.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?
chore: upgrade to 0.4.0+v1.19.0
Image tag changes
Recipe version: 0.3.0+v1.16.0 → 0.4.0+v1.19.0
Release notes summary (v1.17.0 – v1.19.0)
Operator Action Required
None. No breaking changes across v1.17.0–v1.19.0. AUTO_MIGRATIONS=true handles DB migrations automatically on next deploy.
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@b88845fa✅ passedfull logs · dashboard
chore: upgrade to 0.3.0+v1.17.0to chore: upgrade to 0.4.0+v1.19.0!testme
🌻 cc-ci —
lasuite-meet@609be200✅ passedfull logs · dashboard
Closing in favour of #5. This branch had drifted out of sync with upstream main: its
0.4.0+v1.19.0commit re-introducedrenovate.json, the README docs (chrome-on-mobile, sysctl tuning, port table), and the.env.sampleTURN_DOMAIN fix — all of which are already merged upstream and identical there. #5 branches off current upstream main and contains only thecompose.ymlversion bump.Pull request closed