Create and optionally push the next Kubernetes-style release tag (vX.Y.Z) from a release-X.Y branch by resolving the remote branch tip, computing the next patch tag, and tagging the commit directly without checking out the branch. Use when the user wants to tag a release, create a version tag, or mentions release tagging, cutting a release, or bumping a patch version.
Cut a new stable release tag for a Kubernetes-style release branch:
release-X.YvX.Y.Z (patch bump)Use scripts/create_release_tags.py to:
<remote>/release-X.YMultiple branches can be tagged in parallel since the script never checks out or modifies the local working tree.
Replace <SKILL_DIR> with the path of this skill directory.
Plan only:
python3 <SKILL_DIR>/scripts/create_release_tags.py --repo . --branch release-1.34
Create the tag locally:
python3 <SKILL_DIR>/scripts/create_release_tags.py --repo . --branch release-1.34 --create
Create and push the tag:
python3 <SKILL_DIR>/scripts/create_release_tags.py --repo . --branch release-1.34 --push
upstream. Override with --remote <name>.release-X.Y, pass --series X.Y.--sign for signed tags.--force-branch is a no-op kept for backward compatibility.Fetch the remote branch and tags:
git fetch upstream --prune --tags
Find the latest stable tag merged into the branch:
git tag --merged upstream/release-1.34 --list 'v1.34.*' --sort=version:refname | grep -E '^v1\.34\.[0-9]+$' | tail -n1
Create and push an annotated tag at the remote branch tip:
git tag -a -m "v1.34.7" v1.34.7 upstream/release-1.34
git push upstream v1.34.7