Aident logoAident logo centerAident Loadout
Use CasesPricingDocs
ENStart Now
AppsGitHub ToolsGithub Create A Release
GitHub Tools

Github Create A Release

Creates a release in a GitHub repository for a specified tag; the tag must be unique for published releases, and if a `discussion_category_name` is given, it must already exist.

Write actionRisk level 2 of 5OAuth connection
Use Github Create A Release

Pricing and limits

Aident logo

Product

Aident LoadoutAident Playbook EditorOpen-CUAK

About

AppsSkillsUse CasesDocsBlogPricingDownloadsPrivacy PolicyTerms of Service

Alternatives

vs Composiovs Zapier
llms.txtGet an AI summary of Aident LoadoutSummarize with ChatGPTSummarize with ClaudeSummarize with GeminiSummarize with Perplexity

© Aident Labs, 2024-2026

Pricing
Free
Unified payment
Not currently supported

Inputs

  • bodystring
    A detailed description of the release. Markdown formatting is supported.
  • namestring
    The title of the release. If omitted and `generate_release_notes` is false, it defaults to the `tag_name`.
  • repostring
    Required
    The name of the repository, without the .git extension. This field is not case-sensitive.
  • draftboolean
    Set to `true` to create an unpublished (draft) release. Defaults to `false`.
  • ownerstring
    Required
    The account owner of the repository (username or organization name). This field is not case-sensitive.
  • tag_namestring
    Required
    The name of the tag for this release. This tag must be unique for published releases.
  • prereleaseboolean
    Set to `true` to identify this release as a pre-release. Defaults to `false`.
  • make_lateststring
    Specifies if this release should be marked as the latest for the repository. Draft releases and prereleases cannot be set as 'latest'.
  • target_commitishstring
    Specifies the commitish value (e.g., branch name, tag name, or commit SHA) from which the Git tag is created. Defaults to the repository's default branch if the tag specified in `tag_name` doesn't exist yet.
  • generate_release_notesboolean
    Set to `true` to automatically generate the release title (`name`) and description (`body`) from the commit history since the last release. Defaults to `false`.
  • discussion_category_namestring
    If specified, a new discussion will be created in this category and linked to the release. The category must already exist in the repository's discussions.

Observable output

  • data
    Required
    Data from the action execution
  • errorstring
    Error if any occurred during the execution of the action
  • successfulboolean
    Required
    Whether or not the action execution was successful or not

Skills that use this Action

Related use cases

No verified related use cases are linked yet.

Official source

Provider source

Skills that use this Action

No published Skills explicitly reference this Action yet.