From 5916cf15ad775d0f1e758d84d80234cd98d943e4 Mon Sep 17 00:00:00 2001 From: Harshit Jain <48647625+Harshit28j@users.noreply.github.com> Date: Sat, 21 Feb 2026 10:40:31 +0530 Subject: [PATCH] Update docs/my-website/docs/troubleshoot/rollback.md Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com> --- docs/my-website/docs/troubleshoot/rollback.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/my-website/docs/troubleshoot/rollback.md b/docs/my-website/docs/troubleshoot/rollback.md index e4a5a0cbd99..ae0831254a4 100644 --- a/docs/my-website/docs/troubleshoot/rollback.md +++ b/docs/my-website/docs/troubleshoot/rollback.md @@ -2,7 +2,7 @@ This guide outlines the process for safely rolling back a LiteLLM Proxy deployment to a previous version. -We recommend rolling back to the previous [stable release](https://github.com/BerriAI/litellm/releases). Stable releases come out every week and follow the `main-stable` tag convention. +We recommend rolling back to the previous [stable release](https://github.com/BerriAI/litellm/releases). Stable releases come out every week and follow the `main-v-stable` tag convention (e.g., `main-v1.77.2-stable`). ## 1. Determine Rollback Scope