joeds13/annover
AnnoVer versioning — bump releases or update image tags in a gitops repository
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| repository | GitOps repository to update (owner/repo). When set alongside 'image', the action runs in deploy mode: it checks out this repo, updates the image tag, commits, and pushes. | no | "" |
| token | GitHub token. In bump mode this is used to push tags and create releases (defaults to the built-in GITHUB_TOKEN). In deploy mode this must be a PAT with write access to the gitops repository. | no | ${{ github.token }} |
| image | Container image name to update in the gitops repo (e.g. ghcr.io/owner/app). Setting this input activates deploy mode. | no | "" |
| tag | New image tag to deploy (e.g. 2026.4). | no | "" |
| path | Local directory name to check the gitops repo out into. Only used in deploy mode. | no | _annover_gitops |
| file | Specific file (relative to the gitops repo root) to update. When omitted, annover searches all YAML files for the image reference. | no | "" |
| no-release | Skip creating a GitHub release (bump mode only). | no | false |
| dry-run | Print what would happen without making any changes. | no | false |
| version | annover CLI version to install. Defaults to "latest". | no | latest |
Outputs
| name | description |
|---|---|
| version | In bump mode: the version that was created. In deploy mode: the tag that was deployed. |