da4ndo/Rust AUR Release Deploy

GitHub Action for building Rust applications, creating GitHub releases, and preparing PKGBUILD for AUR deployment

Trust Signals

workflow.ymlSHA-pinned

uses: da4ndo/rust-aur-release-deploy@b8a3f7ef7c303b363adffdebb96f2d8df3b04478 # v2

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

name	description	required	default
version	Version to deploy (e.g. v1.0.0). If not provided, uses the latest release tag.	no	—
package_name	Name of your package	yes	—
platform	Platforms to build for (linux, windows, or both)	no	linux
linux_files	List of additional files to include in the Linux tar.gz archive (JSON array)	no	[]
windows_files	List of additional files to include in the Windows release (JSON array)	no	[]
release_files	List of additional files to include in the GitHub release but not in platform archives (JSON array)	no	[]
rel	Release number for AUR package	no	1
prepare_aur	Whether to prepare PKGBUILD for AUR deployment	no	true
pkgbuild	Path to the PKGBUILD file to use for AUR deployment	no	""
pkgbuild_output_path	Path where the prepared PKGBUILD file should be saved	no	./prepared_pkgbuild/PKGBUILD
is_git_package	Whether this is a -git deployment (skips build, release creation, and file preparation)	no	false
is_bin_package	Whether this is a -bin deployment (use prebuilt binaries from release assets)	no	false
prerelease	Whether to mark the release as a prerelease	no	false
auto_release	Whether to automatically create/update GitHub release (ignored if is_git_package is true)	no	true

name	description
version	The version that was deployed
linux_archive	Path to the Linux tar.gz archive
linux_sha256	SHA256 sum of the Linux archive
windows_archive	Path to the Windows zip archive
windows_sha256	SHA256 sum of the Windows archive
pkgbuild_path	The path to the prepared PKGBUILD file