Prepare shared component generations and adopt updates per worker - #326
Merged
Merged
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
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.
Component updates previously repeated dependency preparation across saved workspace/bundle combinations and waited for all conversations to become idle. This release prepares only currently offered app profiles in one dependency transaction and makes a qualified generation available to new workers while active work finishes on its existing generation.
Validation:
UpdateManager.check/install: availability check 1.33 s; component qualification and promotion 15.05 s with five offered profiles. This is a warm fixture measurement, not a guarantee for cold downloads or every machine.Conflicting offered requirements reject the candidate instead of choosing a source implicitly. Shared source-object garbage collection remains conservative until references are proven absent. Native transcript storage is unchanged. This uses the existing worker lifecycle boundary and does not add the broader architecture plan's protocol migration. Published-instance adoption and real-account acceptance remain separate from these fixture checks.