Add Java SDK capability manifest and compatibility matrix - #71151
Merged
Conversation
jason810496
requested review from
amoghrajesh,
ashb,
bugraoz93,
gopidesupavan,
jscheffl,
potiuk and
uranusjr
as code owners
August 5, 2026 05:53
boring-cyborg
Bot
added
area:dev-tools
area:java-sdk
backport-to-v3-3-test
phanikumv
reviewed
Aug 5, 2026
uranusjr
reviewed
Aug 7, 2026
uranusjr
reviewed
Aug 7, 2026
uranusjr
reviewed
Aug 7, 2026
jason810496
marked this pull request as draft
August 8, 2026 07:20
jason810496
force-pushed
the
ci/java-sdk/compat-matrix
branch
2 times, most recently
from
August 10, 2026 02:50
32576e5 to
a8e0e13
Compare
jason810496
marked this pull request as ready for review
August 10, 2026 03:19
The Language SDK conformance spec defines which TaskInstance states and capabilities a Language SDK may declare, but nothing lets an SDK say what it actually supports. Readers of the Java SDK docs cannot tell which parts of the spec the runtime implements today — and the gaps are real and moving (native Dag authoring, deferral, and the state stores are not there yet), so an unqualified "see the conformance spec" overstates what a Java task can do. The manifest is hand-authored YAML rather than something derived from the SDK's own sources: it describes the SDK instead of being part of it, so it has no business shipping in a user's runtime dependencies, and deriving it would mean a JDK and a Gradle run in a hook that only ever renders a table. It therefore sits above every subproject in settings.gradle.kts, where no source set can pick it up. Validation carries the weight a compiler would have: unknown keys are rejected along with missing ones, since it is the only thing standing between a typo and a wrong published table. A prek hook regenerates the contributor-facing README table and the Dokka module doc from the manifest, so a capability landing in the runtime is a one-line edit rather than three tables to update by hand. The shared schema, SDK registry, and renderer let the Go and TypeScript SDKs declare theirs the same way.
jason810496
force-pushed
the
ci/java-sdk/compat-matrix
branch
from
August 16, 2026 08:14
a8e0e13 to
c34b93a
Compare
jason810496
requested review from
phanikumv and
uranusjr
and removed request for
uranusjr
August 17, 2026 01:51
uranusjr
reviewed
Aug 17, 2026
uranusjr
reviewed
Aug 17, 2026
uranusjr
reviewed
Aug 17, 2026
jason810496
marked this pull request as draft
August 17, 2026 08:20
Contradictory native-Dag declarations could pass validation while being rendered as not applicable. Published matrix tables also need to remain readable without forcing unrelated headers onto one line.
1 task
jason810496
marked this pull request as ready for review
August 18, 2026 08:09
jason810496
commented
Aug 18, 2026
jason810496
left a comment
jason810496
left a comment
Member
Author
There was a problem hiding this comment.
Thanks TP for the review.
uranusjr
approved these changes
Aug 20, 2026
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
3 participants
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.
Why
The Language SDK conformance spec (#70717) defines which TaskInstance states and capabilities a Language SDK may declare, but nothing lets an SDK say what it actually supports.
This makes that support machine-readable and generates the docs from it.
How
Rejected Alternative
Verfication
Was generative AI tooling used to co-author this PR?