New Tag

Workflow

Inspect the release convention

• Check git status --short, the current branch, and recent tags before changing versions.
• Inspect .github/workflows/ for tag patterns such as v*, package filters, build jobs, and publish jobs.
• Inspect package manifests and release scripts to determine which package version should drive the new tag.

Choose the version plan

• Follow the repository's existing tag pattern unless the user explicitly wants to change it.
• Bump only the packages affected by the release.
• Bump shared packages when their changed code is consumed by a package that will be published from this tag.
• Keep compatibility gates unchanged unless the new release actually requires a higher minimum version.
• If the worktree contains unrelated changes, stop and ask before including them in the release.

Apply the version changes