This is an automated email from the ASF dual-hosted git repository.
amoghrajesh pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow-site.git
The following commit(s) were added to refs/heads/main by this push:
new d1cb6480b6 Unifying version in 3.3.0 blogpost
d1cb6480b6 is described below
commit d1cb6480b60833de54c0c7af8995baf517c93c5e
Author: Amogh Desai <[email protected]>
AuthorDate: Wed Jul 8 11:57:21 2026 +0530
Unifying version in 3.3.0 blogpost
---
landing-pages/site/content/en/blog/airflow-3.3.0/index.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/landing-pages/site/content/en/blog/airflow-3.3.0/index.md
b/landing-pages/site/content/en/blog/airflow-3.3.0/index.md
index f0a6ca5a1c..9b1c961cd8 100644
--- a/landing-pages/site/content/en/blog/airflow-3.3.0/index.md
+++ b/landing-pages/site/content/en/blog/airflow-3.3.0/index.md
@@ -121,7 +121,7 @@ state_store_backend = mypackage.state.CustomStateBackend
Airflow has always been Python-first for both orchestration *and* task logic.
3.3 keeps the orchestration in Python but lets individual **task
implementations** be written in Java or Go and run on the **standard Airflow
workers** you already operate. A new **Coordinator** layer routes a task to its
language runtime — `JavaCoordinator` for the JVM, `ExecutableCoordinator` for
self-contained native binaries such as Go — runs your code there, and proxies
Variables, Connections, and XComs ba [...]
-> ⚠️ **Experimental in 3.3.** The SDK APIs and wire protocol may change
between releases. The Java and Go SDKs ship as **separate artifacts** (a
Maven/Gradle dependency and a Go module + coordinator), **not** in the
`apache-airflow` pip package.
+> ⚠️ **Experimental in 3.3.0** The SDK APIs and wire protocol may change
between releases. The Java and Go SDKs ship as **separate artifacts** (a
Maven/Gradle dependency and a Go module + coordinator), **not** in the
`apache-airflow` pip package.
## Author two things: a Python stub Dag + the language task
@@ -265,7 +265,7 @@ Task retry behaviour is now pluggable. In addition to a
fixed `retries` count, y
You can now designate a task as a Dag's **result** with the `@result`
decorator, then call `GET /api/v2/dags/{dag_id}/dagRuns/{dag_run_id}/wait` to
block until the run finishes and get the value back. The endpoint streams
newline-delimited JSON (NDJSON) — the run state as it progresses, and on
completion the result task's return value keyed by task id — which makes it
easy to embed an Airflow Dag behind an API endpoint.
-> ⚠️ **Experimental** in 3.3.0 and may change in future releases. (#64563)
+> ⚠️ **Experimental in 3.3.0** and may change in future releases. (#64563)
# 📦 Dag Bundle Version Control on Clear, Rerun, and Backfill
