<![CDATA[Managing CloudronVersions.json]]>The new Community App functionality is a real bonus, so thanks once more to the Cloudron team for implementing it.

The app update functionality provided (new entry in CloudronVersions.json) really helps with the build cycle, testing changes etc., without time-consuming repeat setup of app environment etc, before it even gets to a MVP release stage.

However that does result in a quite big CloudronVersion.json - on one app in dev, it is 60kb. Not a problem as such. But I wonder if we really need to keep such a big history of the app's dev cycle, 0.0.1, 0.0.2 etc all the way up to say 1.0.0 and beyond. Especially when the older entries become redundant by being explicitly revoked or by representing early prototyping with breaking changes.

I have tested just trimming CloudronVersions.json, removing early entries. It seems to have no ill effects providing the json structure is honoured. So my intention is to prune the versions file of dev release before an app becomes released.

So in terms of managing CloudronVersions.json, I'm interested in Cloudron team's thoughts or any advice.
Maybe you did not expect the functionality to be used like, so did not expect a large versions file. But I can easily see it growing to to 200k in some cases. Not a problem technically, but nevertheless ...

]]>https://forum.cloudron.io/topic/15358/managing-cloudronversions.jsonRSS for NodeTue, 07 Apr 2026 23:54:12 GMTTue, 07 Apr 2026 13:45:47 GMT60<![CDATA[Reply to Managing CloudronVersions.json on Tue, 07 Apr 2026 14:22:31 GMT]]>@James thank you
I had not initially intended to use CloudronVersions in this way, but it is a real time saver.

Yep, once an app is published, probably no trimming (unless very old revoked versions).

]]>https://forum.cloudron.io/post/123016https://forum.cloudron.io/post/123016Tue, 07 Apr 2026 14:22:31 GMT<![CDATA[Reply to Managing CloudronVersions.json on Tue, 07 Apr 2026 13:55:26 GMT]]>Hello @timconsidine

@timconsidine said:

I have tested just trimming CloudronVersions.json, removing early entries. It seems to have no ill effects providing the json structure is honoured. So my intention is to prune the versions file of dev release before an app becomes released.

Exactly.
Since the packager (you) is the maintainer of the versions, it is completely up to the maintainer which versions to supply in the CloudronVersions.json file.
The only issue that could arise is that if some had installed version 0.0.1 and created a backup, is now on version 2.0.0 and wants to restore the backup of version 0.0.1 and the version is missing from the CloudronVersions.json it could lead to an error.
Other than this specific scenario, it should be no issue to truncate versions.

]]>https://forum.cloudron.io/post/123007https://forum.cloudron.io/post/123007Tue, 07 Apr 2026 13:55:26 GMT