Repository navigation
fix: preserve and reconcile local dev deployments - #900
Merged
Merged
Conversation
|
Enclave skipped this draft pull request. It will run automatically when you mark the PR as Ready for review. |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
alongubkin
marked this pull request as draft
October 6, 2026 06:18
…1255-persistent-local-dev
…1255-persistent-local-dev
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.
Preserve the local manager database, deployment identity, and resource data across full
alien devrestarts. Refresh session environment variables while exclusively owning the stopped state; own manager HTTP tasks and native workers through cancellation and graceful shutdown. Recover unchanged removed local containers through normal reconciliation, with local setup authority scoped to the local provider.Create and watch deployments explicitly in
local-dev. Cleanup requires a unique Local match in that group and rejects incomplete lists. Legacy records outside that group require explicit ID or group/name selection; migration preserves identity and resource state, rejects name collisions, and prevents implicit adoption or duplicate creation.Includes the teardown compatibility changes from #899; land #899 first. The PR retains main as its base.
Validation: 14 local lifecycle tests and 6 combined destroy tests passed, including real SQLite state preservation/collision checks and HTTP other-group cleanup rejection. Missing explicit migration targets fail before creating state, including on a fresh project. The HTTP fixture enforces the manager’s group requirement for name filters. Final combined CLI all-features build passed. Actual runtime validation of the affected fresh-start/teardown flow passed. Latest normal required CI passed on 4053a7d, including Rust, TypeScript, worker integration and the aggregate check.
Combined CLI application validation passed all 11 conformance suites (113 checks), including native workers, uploads, nested projection, authentication and build tokens.
Following the main update, all 26 affected checks passed: 6 cleanup, 14 local lifecycle, 3 manager HTTP lifetime, 1 lock retention and 2 real Docker identity tests. All-features CLI build and actual application same-ID/data restart, direct native uploads, exact nested projection, unchanged-container recovery and CLI-only shutdown passed on 4053a7d. Required normal CI passed for this head.