fix(docs): correct Docker image tag in v1.82.0 release notes

[anuragprafulla]

Summary

• Fixes the Docker image tag in the v1.82.0 release notes: main-1.82.0-stable → main-v1.82.0-stable
• The v prefix was missing, which would cause docker pull to fail with the copied command

Test plan

• No code changes — documentation fix only

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
litellm	Ready	Preview, Comment	Mar 13, 2026 10:26am

[CLAassistant]

All committers have signed the CLA.

[greptile-apps]

Greptile Summary

This PR corrects a typo in the v1.82.0 release notes where the Docker image tag was missing the v prefix, changing ghcr.io/berriai/litellm:main-1.82.0-stable to ghcr.io/berriai/litellm:main-v1.82.0-stable. Without this fix, users copying the docker run command directly from the release notes would get a docker pull failure because the tag main-1.82.0-stable does not exist in the GitHub Container Registry.

• Fix: Added missing v prefix to the Docker image tag on line 29 of docs/my-website/release_notes/v1.82.0.md
• Impact: Documentation-only change; no code, tests, or configuration is affected
• Correctness: The corrected tag main-v1.82.0-stable follows the same convention used in all other LiteLLM release notes (e.g., main-v1.81.14-stable)

Confidence Score: 5/5

• This PR is safe to merge — it is a trivial, documentation-only fix with no code changes.
• The change is a single-character addition (v) in a Markdown release-notes file. It corrects an invalid Docker tag to match the established versioning convention, carries zero risk of regression, and requires no testing beyond verifying the tag exists in the registry.
• No files require special attention.

Important Files Changed

Filename	Overview
docs/my-website/release_notes/v1.82.0.md	Single-character fix: adds missing v prefix to Docker image tag in the docker run snippet (main-1.82.0-stable → main-v1.82.0-stable). Change is correct and matches the established tagging convention used in other release notes.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[User reads v1.82.0 release notes] --> B{Copy docker run command}
    B -- Before fix --> C["ghcr.io/berriai/litellm:main-1.82.0-stable"]
    B -- After fix --> D["ghcr.io/berriai/litellm:main-v1.82.0-stable"]
    C --> E["❌ docker pull fails\n(tag does not exist)"]
    D --> F["✅ docker pull succeeds\n(tag exists in GHCR)"]

Loading

_{Last reviewed commit: d7c6b95}