Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request]: Add a latest-release tag to the docker image #12853

Open
DanielWeigl opened this issue Apr 17, 2023 · 3 comments
Open

[Feature Request]: Add a latest-release tag to the docker image #12853

DanielWeigl opened this issue Apr 17, 2023 · 3 comments
Assignees

Comments

@DanielWeigl
Copy link

Is your feature request related to a problem? Please describe.

Currently each commit on master triggers a new tag on your docker image and releases dont have a dedicated tag. We have an automated update check on our cluster (keel) which automatically depolys the most recent version if a tag gets updated.

Describe the solution you'd like

Can you add here and here something along:

type=semver,pattern=v{{major}}-latest

(untested)

So that its possible to subscribe to the most recent major version tag.

Describe alternatives you've considered

No response

Additional context

(based on documentaion from https://github.com/docker/metadata-action#typesemver )

@welcome
Copy link

welcome bot commented Apr 17, 2023

👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can.

@snipe
Copy link
Owner

snipe commented Apr 17, 2023

and releases dont have a dedicated tag

They do though, so I'm not sure what problem we're solving here.

https://hub.docker.com/r/snipe/snipe-it/tags

You can def see the master and dev builds, but under that, you see the tagged releases.

@DanielWeigl
Copy link
Author

Yes, but its not possible to use one tag (eg. v6-latest or latest-release) to get the most recent release. If you follow the tag master or latest we get an update for each push to master, which not necessarily is a release. And if you subscribe to an explicit release tag (v6.1.0) we would never get automated updates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants