A GitHub Action to create releases via the GitHub Release API, automating release creation in workflows.
actions/create-release is a GitHub Action that automates the creation of releases using the GitHub Release API. It allows developers to trigger release generation as part of their CI/CD pipelines, typically on events like tag pushes, and supports customizing release details such as names, descriptions, and draft status. This eliminates manual release creation and integrates release management directly into automated workflows.
Developers and DevOps teams using GitHub Actions for CI/CD who want to automate their release process, especially those managing versioned software projects with frequent releases.
It simplifies release automation by providing a native GitHub Action that directly interfaces with GitHub's API, requiring minimal configuration and no external tokens. Its seamless integration with GitHub Actions workflows and compatibility with asset upload actions makes it a convenient choice for teams already using GitHub's ecosystem.
An Action to create releases via the GitHub Release API
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Uses the built-in GITHUB_TOKEN for authentication, eliminating manual token setup and ensuring seamless compatibility with GitHub Actions workflows, as highlighted in the example workflow.
Supports specifying release names, descriptions via direct input or body_path, and draft/prerelease status, allowing flexible customization based on the GitHub Release API inputs.
Outputs an upload_url that integrates with other actions like @actions/upload-release-asset, enabling automated asset attachment in subsequent workflow steps.
Can create releases for external repositories by specifying owner and repo inputs, useful for managing cross-repo release workflows without additional configuration.
The repository is explicitly marked as archived with no updates or support from GitHub, meaning issues and pull requests are not addressed, posing risks for production use.
As development has ceased, it lacks newer features and optimizations found in maintained alternatives like elgohr/Github-Release-Action, potentially limiting workflow flexibility.
With no maintenance, the documentation may not reflect current GitHub API changes or best practices, increasing setup errors and compatibility issues over time.