runbook: 2026-11-08 upgrade window — LiteLLM 1.103.2→1.108.0 + LibreChat overlay 1.4.5→1.4.8
Prepared and validated on 2026-11-06; nothing deployed. Candidates: - code/litellm branch upgrade-v1.108.0 → image 1.0.0-20261106-9e25578 (8/8 patches verified in the built image and in a live sandbox run; image-gen spend row verified nonzero twice — fake + real Regolo probe; 36 additive migrations; budget_reset_at + portal API shapes unchanged). - co-op/librechat-custom branch bump-appstore-1.4.8 → overlay 20261106-c2aec74 (appstore 1.4.8 = tooling bumps on the same 0.8.8 upstream; all overlay anchors verified against the real 1.4.8 image — no porting needed). Runbook: LiteLLM first, member-scope verification, rollback = previous tag per app, window estimate 45-60 min.
This commit is contained in:
1 parent
fcd4ac6943
commit
816961fb2d
2 files changed
+240
No files matched your search
@@ -30,6 +30,7 @@ Read it on the web here: <https://git.inference.coop/co-op/ops-docs>
|
||||
| `maintenance/librechat-sandbox.md` | Operating the LibreChat evaluation instance (config, overlay image, key sync, pitfalls) |
|
||||
| `maintenance/backups.md` | The two backup systems (agent-host restic + Cloudron app backup): schedules, retention, the cache split and the grouping fix |
|
||||
| `maintenance/woodpecker-ci.md` | The self-hosted CI server and agent: build/pin, manual-only trigger, git-lfs, and its not-yet-green state |
|
||||
| `maintenance/2026-11-08-litellm-1.108.0-librechat-1.4.8.md` | The Sunday-evening upgrade-window runbook (gateway → 1.108.0, chat overlay → appstore 1.4.8): candidates, order, exact commands, per-step verification, rollback, window estimate |
|
||||
| `incidents/` | Post-incident write-ups, one file per incident |
|
||||
| `migration/` | The Cloudron server-migration record: the plan, the DNS change sheet, and the captured pre-migration state |
|
||||
| `provider-pricing/` | What each model provider charges, and when it changed (GreenPT, Tinfoil, Regolo, and the decision-model route) |
|
||||
|
||||
Reference in new issue
Block a user