Skip to content

docs: map upstream PR dependencies - #6

Merged
teamhimeh merged 2 commits into
qoncept-forkfrom
codex/document-upstream-pr-dependencies
Oct 23, 2026
Merged

teamhimeh merged 2 commits into
qoncept-forkfrom
codex/document-upstream-pr-dependencies

Conversation

@teamhimeh

@teamhimeh teamhimeh commented Oct 23, 2026 •

Copy link
Copy Markdown
Collaborator

Add pr-dependencies.md to plan contribution of the fork's five JNI fixes to swiftlang/swift-java. The Mermaid graph identifies fixes by their qoncept/swift-java PR numbers (#1–#5), matching how the work is tracked in origin, while its arrows represent prerequisites for upstream submission and merging.

Protocol extension requirement classification (origin #2) precedes requirement naming (origin #3); the other fixes can target upstream main independently. Record origin PR links, the existing upstream PR #938, source branches and commits, dependency rationale, and submission order. Keep upstream PR numbers and statuses distinct from origin tracking and merge status.

Validation:

  • Checked origin PR numbers against their titles and source branches.
  • Checked source patches and upstream PR status against upstream main at 301e3da.
  • Confirmed each of the four independent patches passes git apply --check on that baseline.
  • Confirmed the naming patch fails to apply alone and passes after the protocol extension patch.
  • git diff --cached --check passed.

Documentation only; no runtime code changes.

@teamhimeh
teamhimeh merged commit d603f2e into qoncept-fork Oct 23, 2026
33 of 42 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant