You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 4a88dc7
Browse filesBrowse the repository at this point in the historyBrowse files
Keep the Java SDK capability manifest internal to the build
The manifest model sat at default (public) visibility in the stable
org.apache.airflow.sdk.conformance package, so a type that exists purely to emit
a build-time JSON file shipped in the published artifact and in the Dokka API
reference. That would make every later change to the manifest schema a source and
binary compatibility question for SDK users, for no benefit — nothing outside the
Gradle dump task consumes it. Marking it internal removes it from both surfaces,
and the generically named Document becomes CapabilityManifest now that the name is
no longer public.
The rest hardens the surrounding tooling against ways it could mislead:
the sync hook now re-triggers when its own implementation changes, so editing the
checker cannot leave the manifest unverified; an unsupported dimension carrying a
"since" version is rejected rather than silently rendering as unversioned; the
manifest is decoded as the first complete JSON value instead of slicing to the
last brace, which mis-parses if Gradle ever frames the output; and the JDK gate
fails closed when CI is set but empty. The Dokka column-width rules now only raise
a minimum width rather than forbidding wrapping, so they cannot cause overflow in
unrelated tables that a Markdown-generated table gives no way to exclude.
0 commit comments