release-management

Release Management

Create a tag on the default branch and publish a GitHub release against it, then read, correct or withdraw what has already been published.

Prerequisites

• repo_owner and repo_name for the target repository
• The default branch must be releasable: CI passing, every intended PR merged
• GitHub token with contents: write access

Workflow

Publishing

1. Check the target - call get_latest_sha to see which commit will be tagged
2. Check what is already out - call get_release with no tag for the current latest, or list_releases for the history
3. Create the tag - call create_tag with a semantic version string
4. Publish the release - call create_release against that tag

Correcting a release

1. Call update_release with only the fields that are wrong
2. Publishing again over the same tag also works: create_release updates a tag that already has a release rather than failing

Withdrawing a release

1. Call delete_release, which leaves the tag in place
2. Pass delete_tag=True only when the tag itself was a mistake
3. Deleting a published release breaks any link to it. Ask the user in chat and get an explicit yes first

Tool Parameters

get_latest_sha

Parameter	Type	Description
repo_owner	str	GitHub organisation or username
repo_name	str	Repository name

Returns the SHA of the newest commit on the default branch, or None if the repository has no commits.

create_tag

Parameter	Type	Description
repo_owner	str	GitHub organisation or username
repo_name	str	Repository name
tag_name	str	Tag name, e.g. v1.2.3
message	str	Tag message. Omit for a lightweight tag
sha	str	Commit to tag. Omit to tag the newest commit on the default branch

Pass sha to cut a release from a known commit. Without it the tool resolves the default branch HEAD itself, and what that points at can change between reading it and tagging it.