Repository navigation
Automatically retire older app versions after updates - #455
Draft
Harrison-Xu wants to merge 2 commits into
Draft
Harrison-Xu wants to merge 2 commits into
Harrison-Xu wants to merge 2 commits into
Conversation
This was referenced Nov 18, 2026
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Version updates currently leave old manifests and binaries behind even though the device and web stores show only the latest version. Web publish PRs now replace older manifests, and the shared deployment policy also covers older czdev clients, historical multi-version apps and concurrently merged PRs.
The backend selects the highest Debian version per app, including arm64/all transitions. After deployment, both global and China registries must exclude retired versions and contain the replacement before official Release downloads are revoked. Remaining superseded manifests are removed from current main with a non-forced push that rechecks their identity and the replacement; failures remain retryable. The existing OSS withdrawal pipeline removes retired mirror objects. Contributor fork Releases remain under their owners' control.
The first deployment also reconciles historical multi-version listings. A read-only plan at base 1f7484d found 54 superseded manifests across 31 apps. This PR has not changed live manifests or Release assets.
Validation: 33 regression tests passed, covering Debian ordering, architecture changes, missing replacements, registry presence, concurrent push retries, rollback protection and failed pushes. Workflow YAML and shell syntax checks passed. docs/PUBLISHING.md compares the CLI and web paths.
Companion dev-portal and AppBuilder PRs synchronize templates, stage matching czdev deletions and prevent retired merged PRs appearing indefinitely as publishing. Deploy packages before enabling the new portal lifecycle text.
Companion PRs: CardputerZero/AppBuilder#22 and CardputerZero/dev-portal#25.