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 repo write access

Workflow

Publishing

1. Check the target - call github_get_latest_sha to see which commit will be tagged
2. Check what is already out - call github_get_release with no tag for the current latest, or github_list_releases for the history
3. Create the tag - call github_create_tag with a semantic version string
4. Publish the release - call github_create_release against that tag

Correcting a release

1. Call github_update_release with only the fields that are wrong
2. Publishing again over the same tag fails unless you pass if_exists="update", which overwrites the title and notes and cannot change make_latest or generate_release_notes

Withdrawing a release

1. Call github_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

github_get_latest_sha

Parameter	Type	Description
repo_owner	str	GitHub organisation or username
repo_name	str	Repository name
ref	str | None	Branch, tag or SHA to read. Omit for the default branch

Returns the SHA of the newest commit on ref, or None if the repository has no commits. A ref GitHub cannot resolve is an error rather than None.

The answer is a reading rather than a pin. A push landing afterwards moves it, so re-read it if time has passed.

github_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