[Feature Request] Implementation of a "Stability Watcher" based on Semantic Versioning (SemVer) #806
Description
Problem statement
Problem Description
Currently, many users face the challenge of deciding the "right" time to update a container. Updating immediately on every patch release (e.g., 2.5.1 to 2.5.2) can sometimes lead to instability, while missing the transition to a new minor branch (e.g., 2.5.x to 2.6.0) means staying on an aging version.
The goal is to automate the notification or update process so that it only triggers when a previous version branch is considered "finished" and stable. In developer logic, this is usually signaled when a new Minor version is released.
Proposed Solution: The "Stability Watcher"
I suggest implementing a feature that allows DockHand to monitor the repository and only trigger actions (notifications or updates) based on specific Semantic Versioning (SemVer) logic.
How it should work:
The system should understand the Major.Minor.Patch structure:
Major (X.0.0): Breaking changes.
Minor (0.X.0): New features, but backward compatible.
Patch (0.0.X): Bugfixes and stability improvements.
The "Stability Watcher" would allow users to ignore all patch updates within their current minor version and only notify them once the Minor digit increases.
Example Scenario:
Current version: 2.5.4
The system ignores 2.5.5, 2.5.6, etc.
As soon as version 2.6.0 is detected on Docker Hub, the system triggers a notification.
User Benefit: The user knows that the 2.5.x branch is now "mature," and it is the perfect time to move to the new stable 2.6.x release.
Technical Inspiration (DIUN Logic)
Currently, this can be achieved via workarounds using tools like DIUN (Docker Image Update Notifier) and complex Regex filters such as:
diun.filter.tag=^2.[6-9]..*$
Integrating this logic natively into DockHand would significantly improve the user experience. Instead of manual Regex, a simple toggle or label like dockhand.watch=minor_jump would be much more efficient.
Benefits
Stability: Users avoid "update fatigue" from constant patch releases.
Automation: Updates happen exactly when a version branch reaches maturity.
Precision: Better alignment with professional SemVer standards.
are you anderstand me? can you make this in this epic greate DockHand? =D
Proposed solution
null
Alternatives considered
No response
Additional context
No response