2ngaos/Release Trigger Action
A reusable action to handle version release and build information
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Maintainedlast commit Dec 20, 2025
- License
- None
Pinned Snippet
uses: 2ngaos/release-trigger@4b9d08a450737f1cba730c2e35fd0408bb71f8e6 # v1.2.7tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| gpg_private_key | GPG secret key for signing commits and tags | yes | — |
| gpg_passphrase | Passphrase for the GPG key | yes | — |
| git_user_email | Email for git commits | yes | — |
| git_username | Username for git commits | yes | — |
| git_token | GitHub token for accessing GitHub API | yes | — |
| version_file_path | Path to the version file (auto-detected if not provided) | no | — |
| release_branch | Name of the release branch | yes | — |
| bump_script | Path to the bump script (language-specific defaults if not provided) | no | — |
| release_sha | Release SHA | no | — |
| working_directory | Working directory | yes | . |
| language | Project language (rust, python, js, ts, or auto-detect) | no | auto |
Outputs
| name | description |
|---|---|
| release_version | The version of the release |
| pr_log | Log of pull requests |
| build_number | The build number |