ZimaOS App Store updates were not governed by a simple rule such as “always update within seven days of upstream.” In the November 2025 source thread, Zima-Giorgio said app versions were manually maintained. He also explained that service applications might intentionally lag the newest upstream release because stability matters, while availability-breaking issues receive higher priority.
Current App Store 2.0 changes how app catalogs are built and delivered, but it does not magically create a guaranteed maintenance cadence. The v2 protocol supports version metadata, update timestamps, release notes, content hashes, and incremental client updates; humans still need to maintain and validate the source app definition.
IceWhale Said Store Versions Were Manually Maintained
The direct source answer was short: App Store software versions were manually maintained, and third-party/community stores might provide newer versions.
This explains why the version in the default catalog can differ from the latest tag published by the upstream application developer.
Latest Is Not Always the Same as Safest
Zima-Giorgio later clarified that service-type applications cannot always be guaranteed to run the newest release immediately. Stability is part of the decision.
For a NAS, a rushed database or major-version upgrade can be more disruptive than running one validated release behind upstream.
Availability-Breaking Issues Receive Higher Priority
IceWhale gave Immich as an example: the App Store package was updated when the older server stopped being compatible with the corresponding mobile app.
This is a useful maintenance principle—breakage that prevents normal use can justify faster action than a feature-only upstream release.
Pull Requests Are Part of the Maintenance Workflow
IceWhale said the team regularly checks the PR list and merges requests as needed. Giorgio encouraged users to submit PRs or create their own stores and specifically asked for help updating Uptime Kuma.
That makes the App Store partly collaborative rather than a closed vendor-only catalog.
Current App Store v2 Has a More Explicit Build and Update Protocol
Current IceWhale developer documentation says the generated v2 store includes fields such as:
-
version; -
update_at; -
release_note; -
content_hash.
Client update checks are driven by the store index and content hash, so unchanged applications are skipped while changed app metadata/Compose files can be fetched incrementally.
See the current App Store v2 build and update model.
Version Metadata Does Not Create a Maintenance SLA
A store can now expose better version/update information, but the protocol does not say every app must be updated within a fixed number of days. Catalog policy and app validation remain human processes.
App Store Version and Docker Image Tag Are Related but Not Identical
A Compose file may pin a specific image tag, use a broad tag such as latest, or reference a multi-service stack with several independent images. The displayed store version can describe the packaged app definition rather than guaranteeing every image inside the stack follows the same version number.
Inspect the Compose definition when exact upstream versioning matters.
Major Application Updates Deserve Extra Caution
Applications such as Nextcloud, Immich, databases, and home-automation platforms can have schema migrations or breaking configuration changes. A delayed App Store update can be intentional while maintainers validate migration behavior.
Back up application data before manually jumping ahead of the catalog.
Community Stores Can Move Faster, with Different Risk
Third-party stores may publish newer versions sooner, but their validation, update cadence, and rollback quality depend on their maintainers. “Newer than default store” is not automatically “better tested.”
App Store Update FAQ
Did IceWhale promise a fixed monthly update cycle?
No. The source says versions were manually maintained and stability/availability influenced priority.
Can users help update App Store apps?
Yes. IceWhale explicitly encouraged pull requests and third-party stores.
Does App Store v2 improve update metadata?
Yes. Current v2 output supports version, update time, release notes, and content-hash-driven update checks.
