phanikumv commented on code in PR #71754: URL: https://github.com/apache/airflow/pull/71754#discussion_r3859621372
########## ts-sdk/capabilities.yaml: ########## @@ -0,0 +1,119 @@ +# Licensed to the Apache Software Foundation (ASF) under one +# or more contributor license agreements. See the NOTICE file +# distributed with this work for additional information +# regarding copyright ownership. The ASF licenses this file +# to you under the Apache License, Version 2.0 (the +# "License"); you may not use this file except in compliance +# with the License. You may obtain a copy of the License at +# +# http://www.apache.org/licenses/LICENSE-2.0 +# +# Unless required by applicable law or agreed to in writing, +# software distributed under the License is distributed on an +# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +# KIND, either express or implied. See the License for the +# specific language governing permissions and limitations +# under the License. +--- +sdk: ts + +min_airflow_version: "3.4" + +# Keep in sync with SUPERVISOR_API_VERSION in src/generated/supervisor.ts. The render hook fails +# if the two disagree. +supervisor_schema_version: "2026-10-30" + +# The runtime terminates a task with SucceedTask, RetryTask, or TaskState (failed/removed); it does +# not yet emit skipped, DeferTask, RescheduleTask, or AwaitInputTask. +states: + success: + supported: true + since: "3.3" Review Comment: Same fix on L31, 34, 37, 53, 60, 64, 68, 72, 79 — on the Java one we tied `since` to MIN_AIRFLOW_VERSION, so these should track whatever L20 becomes. If the first release is genuinely undecided, dropping the `since` keys is legal (the renderer prints "–") and more honest than naming a release that hasn't been cut. ```bash sed -i '' 's/^ since: "3.3"$/ since: "3.4"/' ts-sdk/capabilities.yaml ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
