keyrockpartners/Persistent Build Number
Allocate stable build numbers per key using a JSON file stored on a branch in the current repository.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Activelast commit May 6, 2026
- License
- None
Pinned Snippet
uses: keyrockpartners/bump-build-number@acd394c7966f59fc768f4c3b5ee64c682a9ca90b # v1tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| key | Stable key to look up, such as a commit SHA, tag, or release identifier. If the key already exists, its existing build number is returned. | yes | — |
| branch | Branch used to store the build-number JSON file. | no | build-numbers |
| file | Path to the JSON file on the storage branch. | no | build-numbers.json |
| github-token | Token with contents:write permission for this repository. | yes | ${{ github.token }} |
| committer-name | Name used for commits to the storage branch. | no | github-actions[bot] |
| committer-email | Email used for commits to the storage branch. | no | 41898282+github-actions[bot]@users.noreply.github.com |
| max-attempts | Maximum push-retry attempts when concurrent jobs update the branch. | no | 10 |
Outputs
| name | description |
|---|---|
| build-number | The existing or newly allocated build number for the key. |
| number | Alias for build-number. |
| existed | true if the key already existed; false if this run allocated it. |