Skip to content

docs(claude): reframe internal/<pin>-stable as opt-in bump sandbox #45

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
songkuan-zheng merged 1 commit into from
Jun 4, 2026
Merged

docs(claude): reframe internal/<pin>-stable as opt-in bump sandbox #45

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -130,7 +130,7 @@ The examples below use the current pin `v1.83.10`.
|---|---|---|
| `<pin>-stable` tag — e.g. `v1.83.10-stable` | Immutable upstream pin | yes — never moves |
| `ship/<pin>` — e.g. `ship/v1.83.10` | Long-term ship — advances only via merged `fix/*` PRs | yes |
| `internal/<pin>-stable` — e.g. `internal/v1.83.10-stable` | Upstream-sync working branch | no — collects upstream commits |
| `internal/<pin>-stable` — e.g. `internal/v1.83.10-stable` | **Optional** bump-preview sandbox. Test-merge `upstream/main` here before a version bump to surface conflicts. Not required for routine sync — that's what `scripts/upstream-sync-check.sh` is for | no — accumulates upstream merges if used |
| `litellm_internal_staging` | Pure upstream tracker for `BerriAI/litellm` | tracks upstream |
| `fix/<name>` | Per-bug feature branch | yes — merged into the ship branch |

Expand All @@ -142,7 +142,10 @@ gh pr create --base "$SHIP" --head fix/<name>

The ship branch only moves when a `fix/*` PR merges, so it stays
exactly `TAG + merged fixes`. Fixes never have to rebase against moving
upstream — the upstream-sync churn lives on the upstream-sync branch.
upstream. Routine awareness of upstream drift comes from
`scripts/upstream-sync-check.sh` (see Upstream sync cadence); the
`internal/<pin>-stable` sandbox is opt-in — use it before a version
bump, not as a continuous mirror.

## Cutting an internal release

Expand Down