drctnl/Maintain semantic version releases
Manages version based on GitHub release and validates against it
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Maintainedlast commit Mar 4, 2025
- License
- MIT
Pinned Snippet
uses: drctnl/release@2ef2354737c2b4b141dc62c3bd9aa731e2ba5c05 # v0.3tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| path | Path to file containing the version | — | VERSION |
| prefix | Prefix for the version | — | v |
| token | Personal access token (PAT) used to fetch the repository. The PAT is configured with the local git config, which enables your scripts to run authenticated git commands. The post-job step removes the PAT. We recommend using a service account with the least permissions necessary. Also when generating a new PAT, select the least scopes necessary. [Learn more about creating and using encrypted secrets](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets) | — | ${{ github.token }} |
| pre-release | pre release identifier | — | — |
| fail | Unused currently ... | — | true |
Outputs
| name | description |
|---|---|
| version | Version of the release |