The rc branch previously derived the base version from the highest git tag, which reopened an already-shipped series: after v1.3.21 stable was published, cutting an RC still produced v1.3.21-rc.N. Anchor RCs to latest_stable + patch so a fresh RC after v1.3.21 correctly resolves to v1.3.22-rc.0. Minor/major RCs are cut by running that stable kind first, which is a clearer workflow than the old heuristic. Co-authored-by: Orca <help@stably.ai> |
||
|---|---|---|
| .. | ||
| e2e.yml | ||
| issue-os-labeler.yaml | ||
| pr-size-labeler.yml | ||
| pr.yml | ||
| release-cut.yml | ||
| release-rc.yml | ||
| release.yml | ||
| track-community-prs.yaml | ||