Skip to content

Add docker tags for major/minor/patch versions #7226

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

Open
3 tasks done
Quadrubo opened this issue Aug 29, 2024 · 0 comments · May be fixed by #7791
Open
3 tasks done

Add docker tags for major/minor/patch versions #7226

Quadrubo opened this issue Aug 29, 2024 · 0 comments · May be fixed by #7791

Comments

@Quadrubo
Copy link

Prerequisites

  • I have checked the Wiki and Discussions and found no answer

  • I have searched other issues and found no duplicates

  • I want to request a feature or enhancement and not ask a question

The problem

Description

As of the point of writing this, v0.107.52 is the latest AdGuardHome version.
As I'm manually updating my images and not using something like release, 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:

  • 0.107.52 - Version 0.107.52
  • 0.107.51 - Version 0.107.51
  • ...
  • latest - Version 0.107.52

Proposed solution

I would propose a tag system like this:

  • 0.107.52 - Version 0.107.52
  • 0.107.51 - Version 0.107.51
  • 0.107 - Version 0.107.52
  • 0 - Version 0.107.52
  • latest - Version 0.107.52

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 0.107 and would have automatically gotten the hotfix to 0.107.52.

Alternatives considered and additional information

No response

@RoboMagus RoboMagus linked a pull request Apr 25, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant