feat(app-platform): Add app data migrations#1345
Merged
Merged
Conversation
Add signed app-data schema and migration metadata to app manifests and update planning. - Parse and validate app-data migration declarations in signed bundles - Add migration planning, dry-run execution, snapshots, rollback restore, and write barriers - Expose path-free migration state through Platform API and Web Shell - Add first-party Feed Reader and Trust Graph migration examples - Update release certification evidence and docs for PR-249
Align project docs and agent skills with the app-data migration contract added after 56b9cb7. - Document signed app-data migration rollback and snapshot boundaries - Correct migration command validation wording for host-independent bundle checks - Add migration evidence and ownership notes to app-platform, build, release, and certification skills
Require the local app-data migration runner to fail closed when a full process-lifetime containment boundary is unavailable, instead of relying on process-group cleanup that detached children can escape. Preflight combined dry-run migration outputs across namespaces before apply so aggregate app-data quotas fail before bundle replacement. Update focused tests and release-certification evidence probes for the new containment and dry-run behavior.
Enforce target manifest data quotas against projected migration output, including quota-lowering candidates that do not grow app data. Restart previously running apps after a migration apply failure when bundle rollback and app-data restore complete successfully.
|
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
1 participant
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.
Summary
Test Plan
./gradlew spotlessApply./gradlew :platform-api:test --tests '*AppDataServiceTest.advanceUpdateMigrationDryRunPayload_whenTargetManifestLowersQuota_expectQuotaError' --tests '*AppUpdateServiceTest.apply_whenRunningMigrationApplyFailsAndRollbackSucceeds_expectRolledBackAppRestarted'./gradlew :platform-api:test --tests '*AppDataServiceTest' --tests '*AppUpdateServiceTest'./gradlew :platform-api:testNotes
developfeature/app-data-migrations113cb68e3d fix(app-updates): Harden migration failure handling