Update mechanism of community app

[ekevu123]

My community app Tymeslot (Forum Link) can be set up via Cloudronversions.json now (mine is here).

However, it doesn't seem to find any automated version. This is my workflow:

1. I change the version number in my software everywhere, e.g. CloudronManifest and CloudronVersions
2. I push the changes
3. A github workflow builds the docker image

I am assuming that the auto-update checks whether a docker image is available for the image, but even if it is, I can create a new install, but no update is found, even if I trigger searching for it manually.

Is there anything specific I can do about this?

[ekevu123]

This has been resolved by @nebulon here: https://forum.cloudron.io/topic/15270/tymeslot/11?_=1774263098011

[nebulon]

So the flow to publish a new app version is documented at https://docs.cloudron.io/packaging/publishing#add-a-version

The published CloudronVersions.json has to contain all published package versions. The dockerImage tags itself are not queried by Cloudron for updates, as this is only part of a package. For example a dockerimage itself has no clue about Cloudron addon usage as such. So the list of manifest jsons for each published app is the single source of truth for Cloudron.

[robi]

@nebulon can you enhance the docs to show how multiple versions, 2-3, look like in a versions file with updates?