A GitHub Action that automatically uploads binary artifacts to new GitHub releases.
skx/github-action-publish-binaries is a GitHub Action that uploads binary files and other build artifacts to GitHub releases. It solves the problem of manually attaching distribution files to releases by automating the process within CI/CD pipelines, ensuring that every release is immediately populated with the correct artifacts.
Open-source maintainers and developers who need to automate the distribution of binaries (e.g., compiled executables, libraries, or installers) as part of their release process on GitHub.
Developers choose this action for its simplicity, reliability, and seamless integration with GitHub's release system. It reduces manual effort, eliminates human error in artifact attachment, and works well in combination with other build-focused actions.
Publish binaries when new releases are made.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Uploads files matching a specified pattern (e.g., 'example-*') to newly created GitHub releases upon trigger, automating manual steps as shown in the sample configuration.
Supports uploading to a specific release ID via the `releaseId` parameter, enabling advanced workflows where releases are created programmatically, as detailed in the advanced configuration.
Designed to work seamlessly with other actions like skx/github-action-build, promoting a clean separation of build and publish steps in CI/CD pipelines.
Uses GitHub's built-in GITHUB_TOKEN with configurable write permissions, ensuring secure authentication without manual token setup, though it requires repository settings adjustment.
Focuses solely on uploading artifacts, lacking built-in support for artifact validation, signing, or multi-platform distribution, which necessitates additional actions or custom steps.
Requires configuring the GITHUB_TOKEN with write permissions in repository settings, a step users might forget, leading to 403 errors as warned in the README.
Tightly coupled with GitHub's release system and CI/CD, making it unsuitable for projects using other platforms like GitLab or self-hosted CI solutions.