actions-marketplace-validations/Build and upload Rust binary to GitHub Releases

GitHub Action for building and uploading Rust binary to GitHub Releases

Trust Signals

Scorecard Score: not yet scored
Maintenance Recency: Activelast commit Apr 4, 2026
License: Apache 2.0

Pinned Snippet

workflow.ymlSHA-pinned

uses: actions-marketplace-validations/taiki-e_upload-rust-binary-action@10c1cf6a3da113ad4e60018e386570529aa5f1d3 # no releases — HEAD as of 2026-07-13

tags can be moved; commit SHAs can't. why a SHA?

Inputs

name	description	required	default
bin	Binary names (non-extension portion of filename) to build and upload (whitespace or comma separated list). Note that glob pattern is not supported yet.	yes	—
archive	Archive name (non-extension portion of filename) to be uploaded (variables `$bin`, `$target`, `$tag`, and any string)	no	$bin-$target
target	Target name, default is host triple	no	—
features	Cargo build features to enable (space or comma separated list)	no	—
no-default-features	Whether to disable cargo build default features	no	—
no_default_features	Alias for 'no-default-features'	no	false
all-features	Whether to build with `--all-features` flag	no	false
package	Package names to build (whitespace or comma separated list)	no	—
workspace	Whether to build with `--workspace` flag	no	false
locked	Whether to build with `--locked` flag	no	false
manifest-path	Override cargo manifest path	no	—
manifest_path	Alias for 'manifest-path'	no	—
tar	On which platform to distribute the `.tar.gz` file (all, unix, windows, or none)	no	unix
tar-xz	On which platform to distribute the `.tar.xz` file (all, unix, windows, or none)	no	none
zip	On which platform to distribute the `.zip` file (all, unix, windows, or none)	no	windows
include	Additional files to be included to the archive (whitespace or comma separated list). Note that glob pattern is not supported yet.	no	—
asset	Additional files to be uploaded separately (whitespace or comma separated list). Note that glob pattern is not supported yet.	no	—
leading-dir	Whether to create the leading directory in the archive or not	no	—
leading_dir	Alias for 'leading-dir'	no	false
bin-leading-dir	Create extra leading directory(s) for binary file(s) specified by 'bin' option	no	—
build-tool	Tool to build binaries (cargo, cross, or cargo-zigbuild)	no	—
build_tool	Alias for 'build-tool'	no	—
checksum	Algorithms to be used for checksum (sha256, sha512, b2, sha1, or md5) (whitespace or comma separated list) Note: b2 is not available by default on macOS, install `b2sum` to use it. sha1 and md5 are insecure and strongly discouraged.	no	—
token	GitHub token for uploading assets to GitHub Releases. If not set this option, the GITHUB_TOKEN environment variable will be used. If not set both this option and the GITHUB_TOKEN environment variable, github.token will be used.	no	—
ref	Fully-formed tag ref for this release. If not set this option, the GITHUB_REF environment variable (automatically set by GitHub Actions) will be used.	no	—
profile	The cargo profile to build. This defaults to the release profile.	no	release
dry-run	Build and compress binaries, but do not upload them. Note that some errors are downgraded to warnings in this mode.	no	—
dry-run-intended	Suppress informational warnings for `dru-run` keeping the rest	no	false
dry_run	Alias for 'dry-run'	no	false
codesign	Sign build products using `codesign` on macOS	no	—
codesign-prefix	Prefix for the `codesign` identifier on macOS	no	—
codesign_prefix	Alias for 'codesign-prefix'	no	—
codesign-options	Specifies a set of option flags to be embedded in the code signature on macOS. See the codesign manpage for details.	no	—
codesign_options	Alias for 'codesign-options'	no	—

Outputs

name	description
archive	Archive base name
zip	.zip archive file name
tar	.tar.gz archive file name
tar-xz	.tar.xz archive file name
b2	BLAKE2 checksum file name
sha256	SHA256 checksum file name
sha512	SHA512 checksum file name
sha1	SHA1 checksum file name
md5	MD5 checksum file name