mirror of
https://github.com/binwiederhier/ntfy.git
synced 2026-05-09 08:26:00 +02:00
[GH-ISSUE #1174] Add docker tags for major/minor/patch versions #829
Labels
No labels
ai-generated
android-app
android-app
android-app
🪲 bug
build
build
dependencies
docs
enhancement
enhancement
🔥 HOT
in-progress 🏃
ios
prio:low
prio:low
pull-request
question
🔒 security
server
server
unified-push
web-app
website
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ntfy#829
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Quadrubo on GitHub (Aug 29, 2024).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1174
Description
As of the point of writing this,
v2.11.0is the latest ntfy 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:
v2.11.0- Version 2.11.0v2.10.0- Version 2.10.0latest- Version 2.11.0Desired Behavior
I would propose a tag system like this:
v2.11.0- Version 2.11.0v2.10.0- Version 2.10.0v2.11- Version 2.11.0v2- Version 2.11.0latest- Version 2.11.0This 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
v2and would have automatically gotten the update tov2.11.0.I however will not get the automatic update to
v3.xwhich would be desired for me.@RoboMagus commented on GitHub (May 31, 2025):
Can be closed. Released as of
v2.12.