Feature suggestion: metadata.json

[webysther]

Maybe help everyone support a metadata.json with a list of common projects and their respective common tags and let people create PR, with this the label can be used to override the default settings and use the metadata.json when no label exists when is expected.

[fmartinou]

Hi @webysther ,

I like the idea 👍 I was already thinking about this feature for quite a time but I haven't found the time to add it so far. My primary concern is how to keep these "metadata" easy to maintain without falling into a bottomless pit (because the docker image ecosystem is very disparate).

[webysther]

Hi @webysther ,

I like the idea 👍 I was already thinking about this feature for quite a time but I haven't found the time to add it so far. My primary concern is how to keep these "metadata" easy to maintain without falling into a bottomless pit (because the docker image ecosystem is very disparate).

I think can be used the ideia of renovate bot versioning as a start point, but like the game community, normally metadata catch mostly common use scenarios, we can maybe keep a filter for package and another for provider, with package override provider:

{
  "versioning": ["semver", "poetry", ...],
  "provider": {
     "linuxserver": ["semver"],
     "official": ["semver-coerced"]
     ...
  },
  "package": {
     "linuxserver/wireguard": '^\d{1,2}\.\d{1,2}\.\d{8}$$'
  }
}