prometheus / prometheus/alertmanager
Add docker tags for major/minor/patch versions
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.6k
- Forks
- 2.5k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 61
Description
Description
As of the point of writing this, v0.27.0 is the latest Alertmanager version.
As I'm manually updating my images and not using something like "latest", I have to change the image tag every new release. It would be nice if I wouldn't have to do that for patch releases (minor releases too).
Currently these tags are provided:
v0.27.0- Version 0.27.0v0.26.0- Version 0.26.0latest- Version 0.27.0
Desired Behavior
I would propose a tag system like this:
v0.27.0- Version 0.27.0v0.26.0- Version 0.26.0v0.27- Version 0.27.0v0- Version 0.27.0latest- Version 0.27.0
This would allow pinning to specific version and allows the user to choose which semver types they are okay with auto updating.
I for example would have pinned to v0 and would have automatically gotten the update to v0.27.0.
I however will not get an auto update to v1.x which would be desired for me.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Docker image publishing configuration and release workflow used by Alertmanager, then trace where version and latest tags are generated. Define completion as publishing major and major/minor tags alongside the existing version-specific and latest tags, with behavior checked across subsequent releases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100