Repository navigation
docs: extend upstream PR dependency map through origin #14 - #12
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.
Update
pr-dependencies.mdto cover origin PRs through #14, including source branches and commit SHAs for every feature patch.Extend the upstream dependency graph with the independent enum naming, Optional calls, protocol adapters, and async cancellation fixes, plus the dependent protocol default bridge. Explain the chain
#2 → #3 → #11, its transitive classification prerequisite, and why the other new fixes are independent. Update submission waves and the alternative stacked-PR/rebase workflow while keeping origin and upstream status distinct.Track the generated-output follow-ups from #13 with their corresponding origin #5 and #8 submissions. Record both commit SHAs and explain that they belong in those existing upstream patches rather than adding another dependency between them.
Add the independent actor-property chain
#4 → #14: #14 extends the witness discovery and regression fixtures introduced by #4 to support standardAnyObjectandSendableconstraints. Prefer including #14 with #4 in one upstream submission; describe the merge order and optional stack if they are submitted separately. This chain does not block#2 → #3 → #11.Validation:
mainat301e3da, and the still-open upstream PR JNI: preserve MainActor isolation in synchronous thunks swiftlang/swift-java#938.git diff --checkpassed.