Conversation
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.
Stack services now have durable instance identities and a shared lifecycle API. Each instance owns its configuration, concrete dependencies, and runtime resources, so Functions and schema-tooling databases can operate independently within the same stack. Database instances also expose snapshot and restore operations.
Replace the custom stack shadow-database implementation with service instances across the CLI's shadow, cache, and reset flows. Functions serve reuses the managed Functions instance and leaves it available after CLI exit. Internal workflows use Effect, with one public Promise facade for non-Effect consumers.
Supersedes #6579