-
-
Notifications
You must be signed in to change notification settings - Fork 184
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
[FEAT] Add another versioning support #89
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
The upstream version is not something we can parse safely to anything but |
Hi thanks for quick response. Maybe it would be good to have tag for example "9.7_p1-r3" as alternative to current "version-9.7_p1-r3" ? |
It would not. configure renovate properly against our tagging if you want to use it. |
3rd sentence from my link above: |
Here is what we use now in our "packageRules": [
{
"matchPackageNames": ["ghcr.io/linuxserver/openssh-server"],
"versioning": "regex:^(?<major>\\d+)\\.(?<minor>\\d+)_p(?<patch>\\d+)-(?<build>r\\d)-(?<revision>.+)$"
}
] Maybe not 100% correct but at least Renovate now suggests updates. |
Thanks for sharing ! I've wanted to use version- tag and i ended up with something similar in the end:
|
Is this a new feature request?
Wanted change
I think it would be good to add new versioning docker tag support, like: "9.7_p1-r3"
Reason for change
Currently there is tag called "version-" but its not supported by renovate bot by default. Other images seems to have this kind of versioning scheme:
https://github.com/linuxserver/docker-healthchecks/pkgs/container/healthchecks ( 3.4.20240701 )
https://github.com/linuxserver/docker-mariadb/pkgs/container/mariadb ( 10.11.8 )
Proposed code change
No response
The text was updated successfully, but these errors were encountered: