This is an automated email from the ASF dual-hosted git repository.

amoghdesai pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git


The following commit(s) were added to refs/heads/main by this push:
     new f7ceec4b63b Refine the execution api versioning doc to reflect reality 
(#51152)
f7ceec4b63b is described below

commit f7ceec4b63b6e51e56b41826fe5c4fae410668b1
Author: Amogh Desai <[email protected]>
AuthorDate: Wed May 28 20:20:59 2025 +0530

    Refine the execution api versioning doc to reflect reality (#51152)
---
 contributing-docs/19_execution_api_versioning.rst | 11 ++++++++---
 1 file changed, 8 insertions(+), 3 deletions(-)

diff --git a/contributing-docs/19_execution_api_versioning.rst 
b/contributing-docs/19_execution_api_versioning.rst
index 189aed58a52..c9d45909508 100644
--- a/contributing-docs/19_execution_api_versioning.rst
+++ b/contributing-docs/19_execution_api_versioning.rst
@@ -25,9 +25,14 @@ Why?
 ----
 
 Airflow components (e.g., workers, API servers) could be deployed 
independently. This can lead
-to version mismatches—for example, a worker using Task SDK 1.0.1 (requiring 
Airflow >=3.0.1) while the
-API server is still on 3.0.0. Without versioning, such mismatches can cause 
runtime failures or subtle bugs.
-A strict versioning model allows older clients to continue working with newer 
servers, enabling safe, incremental upgrades.
+to version mismatches—for example, a worker using Task SDK 1.0.0 (requiring 
Airflow >=3.0.0) while the
+API server has been upgraded to 3.0.1. Without versioning, such mismatches can 
cause runtime failures or subtle bugs.
+Enforcing a clear versioning contract ensures backward compatibility and 
allows for safe, incremental upgrades
+across different components.
+
+Note: We're prioritizing backward compatibility, older clients should continue 
to work seamlessly with newer servers.
+Since the client (Task SDK) and server (API) are still coupled, we can look at 
forward compatibility once we have a
+clear versioning strategy between Task SDK and Airflow Core.
 
 Versioning Principles
 ---------------------

Reply via email to