[jason810496]

Release the Java SDK as 1.0.0 (GA) and take its supervisor schema from the published docs site instead of staged, which is a preview and not a release artifact.

-projectVersion=1.0.0-SNAPSHOT
+projectVersion=1.0.0

-val schemaBaseUrl = "https://airflow.staged.apache.org/schemas/supervisor-schema"
+val schemaBaseUrl = "https://airflow.apache.org/schemas/supervisor-schema"

supervisor-schema/2026-10-30.json goes live with the Airflow 3.4.0 docs publish.

Backport to v3-4-test

The vendored java-sdk/sdk/schema/schema.json predates later changes to api_version 2026-10-30, and the version-gated sync never refreshes it. The backport should also copy task-sdk/src/airflow/sdk/execution_time/schema/schema.json from v3-4-stable into it, so 1.0.0 ships with the schema Airflow 3.4.0 speaks.

[uranusjr]

This would break the refresh workflow from #69527 until 3.4 is published live. I think we should merge this after 3.4 core is released and the schema file published instead? (Which means the Java SDK also needs to be released after Airflow 3.4.0 is ready.)

[jason810496]

This would break the refresh workflow from #69527 until 3.4 is published live. I think we should merge this after 3.4 core is released and the schema file published instead? (Which means the Java SDK also needs to be released after Airflow 3.4.0 is ready.)

Does this mean the Java-SDK RC vote can only be held after the 3.4 release?

If we can bear with the voting time, then releasing Java-SDK after 3.4.0 works for me.
Then the next step is 1) wait until 3.4 is published, 2) merge and backport this PR, 3) then we can start the Java-SDK RC.