|
Dear all, can you help me sort out my confusion on this one? I adapted the helm chart guide and used the following sources:
nginx-release:
kind: "githubrelease"
name: "Get the latest nginx version"
spec:
owner: "nginx"
repository: "nginx"
token: '{{ requiredEnv "GITHUB_TOKEN" }}'
username: "XXX"
versionfilter:
kind: "latest"For reasons I think I understand, this reproducibly gave I then added the a sources:
nginx-release:
kind: "githubrelease"
name: "Get the latest nginx version"
spec:
owner: "nginx"
repository: "nginx"
token: '{{ requiredEnv "GITHUB_TOKEN" }}'
username: XXX
typefilter:
latest: true
versionfilter:
kind: "latest"Did updatecli pick the old release 1.30.4 just because it was the "youngest" release according to the release date (3 minutes younger than 1.31.3)? The documentation seems to indicate this: ``Returns the latest release, sorted by release date Is "latest" being used in If so, I think this should be documented more prominently in the helm chart guide as well as in the documentation, as "latest" in Github normally means the latter definition. Maybe switching to "youngest" or "most_recent" or similar would help to avoid this kind of confusion. (And yes, I do think that Github using Kind Regards, |
Replies: 1 comment
|
OK, this is explained in the documentation and I just overlooked it, as it is directly beneath the big and not-well-formatted table with all of the keys. https://www.updatecli.io/docs/plugins/resource/github_release/#_typefilter |
OK, this is explained in the documentation and I just overlooked it, as it is directly beneath the big and not-well-formatted table with all of the keys.
https://www.updatecli.io/docs/plugins/resource/github_release/#_typefilter