Repository navigation
distribution: serialize portable update transactions - #224
Merged
Merged
Conversation
turinglambdaai
force-pushed
the
fix/serialize-update-transactions
branch
2 times, most recently
from
October 13, 2026 00:36
d9bbd67 to
552f640
Compare
turinglambdaai
force-pushed
the
fix/serialize-update-transactions
branch
from
October 13, 2026 00:41
552f640 to
1a6e42a
Compare
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.
Closes #223.
Serializes portable update execution and recovery with both an in-process semaphore and an operating-system file lock derived from the installation target. The target identity remains the same even when callers configure different backup paths, so competing updaters cannot race over shared staging, target, marker, or journal state. Lock acquisition is break-safe; the empty lock file intentionally persists while OS ownership is released automatically on crash.
platform-installationis now an opaque prepared transaction, preventing callers from forging the internal target-lock identity or lifecycle callbacks.The concurrency regression holds one transaction in a separate thread and proves that a second installation for the same target but a different backup path is rejected before the old payload or journal changes.
Local evidence: 211 platform-adapter, public-API, and documentation tests pass after rebasing onto current main.