a-line-services/A-Line Release Pilot

Framework-agnostic release automation with multi-package and multi-ecosystem support

Trust Signals

Scorecard Score: not yet scored
Maintenance Recency: Activelast commit Feb 28, 2026
License: GPL 3.0

Pinned Snippet

workflow.ymlSHA-pinned

uses: a-line-services/release-pilot@0040154ab11ae593ab4437f7a0e975d1fd25b4e9 # v1.2.13

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

Inputs

name	description	required	default
github-token	GitHub token for API access and pushing changes	yes	${{ github.token }}
config-file	Path to release-pilot config file	no	.github/release-pilot.yml
mode	Release mode: stable (full release), dev (pre-release), or check (dry-run report)	no	stable
dry-run	Run without making any changes (useful for testing)	no	false
dev-suffix	Suffix for dev releases (e.g., dev, nightly, alpha, beta, rc)	no	dev
packages	JSON array of package configs (alternative to config file)	no	—
default-bump	Default version bump when no release label is found (major, minor, patch)	no	patch
npm-token	NPM registry token for publishing (configures .npmrc automatically)	no	—
npm-registry	NPM registry URL (default: https://registry.npmjs.org)	no	https://registry.npmjs.org
git-user-name	Git user name for commits (auto-detected from token if not set)	no	—
git-user-email	Git user email for commits (auto-detected from token if not set)	no	—
cargo-token	Cargo registry token for publishing to crates.io	no	—

Outputs

name	description
version	The new version that was released
previous-version	The previous version before the release
bump-type	The version bump type that was applied (major, minor, patch)
released-packages	JSON array of package names that were released
skipped	Whether the release was skipped (true/false)
release-url	URL of the created GitHub release (if any)
tag	The git tag that was created