releases_create - Charter

POST

github_releases_create.py

from charter.packs import github

result = await github.releases_create.ainvoke({"owner": ..., "repo": ..., "tagName": ...})

Requires repo, read:user.

Path parameters

Field	Type	Description
`owner` *	`string`	The account owner of the repository. The name is not case sensitive.
`repo` *	`string`	The name of the repository without the `.git` extension. The name is not case sensitive.

Body

Field	Type	Description
`tagName` *	`string`	The name of the tag.
`targetCommitish`	`string`	Specifies the commitish value that determines where the Git tag is created from. Can be any branch or commit SHA. Unused if the Git tag already exists. Absent, the repository’s default branch.
`name`	`string`	The name of the release.
`body`	`string`	Text describing the contents of the tag. With `generate_release_notes` set, this is placed above the generated notes rather than replacing them.
`draft`	`boolean`	`true` to create a draft (unpublished) release, `false` to create a published one. GitHub publishes when this is absent.
`prerelease`	`boolean`	`true` to identify the release as a prerelease. A prerelease is never returned by `releases_get_latest`.
`discussionCategoryName`	`string`	If specified, a discussion of the specified category is created and linked to the release. The value must be a category that already exists in the repository.
`generateReleaseNotes`	`boolean`	Whether to automatically generate the name and body for this release from the merged pull requests since the last one. If `name` is specified, the specified name will be used; otherwise, a name will be automatically generated.
`makeLatest`	MakeLatest	Whether this release should be set as the latest release for the repository — a string, not a boolean. Drafts and prereleases cannot be set as latest. `legacy` determines the latest release from the creation date and the higher semantic version. GitHub uses ‘true’ for newly published releases.