fix(renovate): track gitea, photoprism and jellyfin again

The gitea values file only set image.tag, and the helm-values manager
needs a repository in the same image block, so the file produced no
dependency at all and gitea never got a PR.

PhotoPrism and Jellyfin use date tags (YYMMDD, YYYYMMDDNN) that docker
versioning reads as a single huge major number, so maxMajorIncrement
threw away every release more than 500 majors away: 212 tags for
photoprism, 42 for jellyfin.

State gitea's registry and repository in the values file, and give both
date-tagged images regex versioning so each release is a minor bump.
This commit is contained in:
vhaudiquet committed 2026-11-09 01:09:36 +01:00
1 parent 82e870d7da
commit 965d4dde35
2 files changed
+19

No files matched your search

+14
View File
@@ -40,6 +40,20 @@
],
"commitMessagePrefix": "chore(kube):",
"commitMessageAction": "bump chart"
},
{
"description": "PhotoPrism tags are YYMMDD dates. Read them as dates so each release is a minor bump instead of a huge major jump that Renovate refuses (maxMajorIncrement).",
"matchPackageNames": [
"photoprism/photoprism"
],
"versioning": "regex:^(?<major>\\d{2})(?<minor>\\d{2})(?<patch>\\d{2})$"
},
{
"description": "Jellyfin tags are YYYYMMDDNN build stamps. Read them as dates so releases are minor bumps instead of huge major jumps that Renovate refuses (maxMajorIncrement).",
"matchPackageNames": [
"jellyfin/jellyfin"
],
"versioning": "regex:^(?<major>\\d{4})(?<minor>\\d{2})(?<patch>\\d{4})$"
}
]
}