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

uranusjr 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 dbf7d644aa6 SDK release templates and documentation (#76807)
dbf7d644aa6 is described below

commit dbf7d644aa66a3d15296459fb19124276f0487e5
Author: Tzu-ping Chung <[email protected]>
AuthorDate: Tue Nov 17 02:48:31 2026 +0800

    SDK release templates and documentation (#76807)
    
    * Add release templates for Go and TS SDKs
    
    * Move SDK verification to common doc
    
    * Share SDK post-vote steps and protect SDK tags
    
    Move the release steps after a vote into the shared language SDK
    release doc, so Go and TypeScript get the dist/release, final tag,
    GitHub release, docs, announce and reporter steps that only Java
    had. Each SDK's DEVELOPMENT.md keeps its own publishing steps: Nexus
    for Java, npm for TypeScript, and the module proxy and pkg.go.dev
    for Go.
    
    Check that the RC commit is still on its release branch before the
    vote and before the final tag. v3-4-test was rewritten during the
    1.0.0 votes, and the TypeScript workflow refused the voted commit.
    
    Add a tag ruleset to .asf.yaml so SDK release tags cannot be deleted
    or moved.
    
    * Wait for the Go tag before querying the proxy
    
    Asking proxy.golang.org or pkg.go.dev for a version before its tag
    is pushed caches a "not found" answer, and the release then stays
    unreachable for up to an hour. Warn about this above the Go
    post-vote steps, and note it on the RC check in the vote checklist.
---
 .asf.yaml                                     |  22 ++
 .github/workflows/java-sdk-release-verify.yml |   4 +-
 dev/README_RELEASE_LANGUAGE_SDKS.md           | 432 ++++++++++++++++++++++++++
 go-sdk/DEVELOPMENT.md                         | 101 ++++++
 java-sdk/DEVELOPMENT.md                       | 257 +--------------
 ts-sdk/DEVELOPMENT.md                         | 118 ++++++-
 6 files changed, 685 insertions(+), 249 deletions(-)

diff --git a/.asf.yaml b/.asf.yaml
index 6423bbc2056..370c1fa04ac 100644
--- a/.asf.yaml
+++ b/.asf.yaml
@@ -175,6 +175,28 @@ github:
               # contributor's fork for a gated pull request or in 
apache/airflow otherwise; until
               # then GitHub lists it on the pull request as expected and 
waiting.
               - context: "CI run started"
+    # Release tags of the language SDKs. The TypeScript npm release workflow 
and the
+    # `ts-sdk-npm-release` environment trust `ts-sdk/*` tags, and the Go 
module proxy caches a
+    # `go-sdk/*` tag's commit forever, so a release tag must not be moved or 
deleted. RC tags are
+    # covered too: they are kept for traceability after a failed vote. 
Committers can bypass it to
+    # repair a bad tag, the same as the CI rulesets above.
+    - name: "Protect language SDK release tags"
+      target: tag
+      enforcement: active
+      conditions:
+        ref_name:
+          include:
+            - "refs/tags/java-sdk/*"
+            - "refs/tags/go-sdk/*"
+            - "refs/tags/ts-sdk/*"
+          exclude: []
+      bypass_actors:
+        - actor_id: 4
+          actor_type: RepositoryRole
+          bypass_mode: always
+      rules:
+        - type: deletion
+        - type: update
     - name: "Branch protection"
       type: branch
       branches:
diff --git a/.github/workflows/java-sdk-release-verify.yml 
b/.github/workflows/java-sdk-release-verify.yml
index ad05c5c122d..d99b5059000 100644
--- a/.github/workflows/java-sdk-release-verify.yml
+++ b/.github/workflows/java-sdk-release-verify.yml
@@ -15,8 +15,8 @@
 # specific language governing permissions and limitations
 # under the License.
 #
-# Runs the Java SDK reviewer checklist ("Verifying a release" in
-# java-sdk/DEVELOPMENT.md) automatically, minus the GPG signature (only the 
release
+# Runs the Java SDK reviewer checklist (dev/README_RELEASE_LANGUAGE_SDKS.md)
+# automatically, minus the GPG signature (only the release
 # manager's key can satisfy that).
 #
 #   * on a pull request touching java-sdk/ -> verify HEAD can produce a source
diff --git a/dev/README_RELEASE_LANGUAGE_SDKS.md 
b/dev/README_RELEASE_LANGUAGE_SDKS.md
new file mode 100644
index 00000000000..d396efcd1b2
--- /dev/null
+++ b/dev/README_RELEASE_LANGUAGE_SDKS.md
@@ -0,0 +1,432 @@
+<!--
+ 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.
+-->
+<!-- START doctoc generated TOC please keep comment here to allow auto update 
-->
+<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
+**Table of contents**
+
+- [The language SDKs](#the-language-sdks)
+- [Verify the release candidate by PMC 
members](#verify-the-release-candidate-by-pmc-members)
+- [Verify the release candidate by 
Contributors](#verify-the-release-candidate-by-contributors)
+- [Check the release candidate commit](#check-the-release-candidate-commit)
+- [After a successful vote](#after-a-successful-vote)
+- [If the vote fails](#if-the-vote-fails)
+
+<!-- END doctoc generated TOC please keep comment here to allow auto update -->
+
+This document describes the release steps shared by the Airflow language SDKs:
+verifying a release candidate, and what to do after the vote. How to build,
+stage and call the vote for each release, and the SDK-specific publishing
+steps, are described in the SDK's own `DEVELOPMENT.md`:
+
+* [Java SDK](../java-sdk/DEVELOPMENT.md#publishing)
+* [Go SDK](../go-sdk/DEVELOPMENT.md#calling-a-release-vote)
+* [TypeScript SDK](../ts-sdk/DEVELOPMENT.md#publishing)
+
+## The language SDKs
+
+Each SDK is voted on as a signed source package in `dist/dev`. The commands
+below use these values; substitute the row for the SDK being verified.
+
+| SDK        | `<SDK>`    | `<TAG>`                    | Convenience binary    
     |
+|------------|------------|----------------------------|----------------------------|
+| Java       | `java-sdk` | `java-sdk/<VERSION>-rc<N>` | Maven, ASF Nexus 
staging   |
+| Go         | `go-sdk`   | `go-sdk/v<VERSION>-rc<N>`  | none (module from the 
tag) |
+| TypeScript | `ts-sdk`   | `ts-sdk/<VERSION>-rc<N>`   | npm, `rc` dist-tag    
     |
+
+The source package is
+`https://dist.apache.org/repos/dist/dev/airflow/<SDK>/<VERSION>-rc<N>/apache-airflow-<SDK>-<VERSION>-src.tar.gz`,
+with its `.asc` signature and `.sha512` checksum next to it.
+
+## Verify the release candidate by PMC members
+
+Anyone on `[email protected]` can (and should) independently verify a
+candidate before voting. Run these checks against the source package in
+`dist/dev`; the release manager runs them too before sending the vote.
+
+### Checksum
+
+Confirm the published SHA-512 matches the downloaded tarball:
+
+```bash
+shasum -a 512 -c apache-airflow-<SDK>-<VERSION>-src.tar.gz.sha512
+```
+
+`shasum` ships with both macOS and most Linux distributions; `sha512sum -c`
+works too on Linux but is not installed on macOS by default.
+
+### Signature
+
+Import the `KEYS` file and verify the GPG signature:
+
+```bash
+curl -O https://downloads.apache.org/airflow/KEYS
+gpg --import KEYS
+gpg --verify apache-airflow-<SDK>-<VERSION>-src.tar.gz.asc \
+    apache-airflow-<SDK>-<VERSION>-src.tar.gz
+```
+
+### Diff against the git tag
+
+Extract the tarball and compare it with a clean checkout of the tag it claims
+to be built from. The extracted top-level directory is
+`apache-airflow-<SDK>-<VERSION>`, without the `-src` suffix that only appears
+in the tarball's own filename:
+
+```bash
+tar xzf apache-airflow-<SDK>-<VERSION>-src.tar.gz
+git clone --branch <TAG> https://github.com/apache/airflow.git tag-checkout
+diff -rq apache-airflow-<SDK>-<VERSION>/ tag-checkout/<SDK>/
+```
+
+They should be identical except for files kept out of the source release via
+`.gitattributes` `export-ignore`, and these expected differences:
+
+* **Java:** the Gradle wrapper scripts and jar (`gradlew`, `gradlew.bat`,
+  `gradle-wrapper.jar`) and `scripts` are omitted, since ASF source releases
+  must not contain compiled code (see [LEGAL-570]). Filter them out with
+  `| grep -vE ': (gradlew|gradlew\.bat|gradle-wrapper\.jar|scripts)$'`.
+* **TypeScript:** the source package may be built from the commit before the
+  tag, where `package.json` has the plain `<VERSION>`; the tag commit only
+  changes it to `<VERSION>-rc<N>` for npm. The vote email names the commit when
+  this applies, and the `version` line in `package.json` is then the only
+  difference.
+
+Any other diff output is unexpected and should block the vote.
+
+If the vote email says the source package was built from a commit before the
+tag, diff the tarball against that commit instead, then confirm the tag adds
+nothing to the SDK directory except the version bump. Limit the diff to the
+SDK directory; the tag usually sits on a release branch, so an unscoped diff
+also lists unrelated commits that landed in between:
+
+```bash
+git -C tag-checkout diff <SOURCE-COMMIT> <TAG> --stat -- <SDK>/
+```
+
+[LEGAL-570]: https://issues.apache.org/jira/browse/LEGAL-570
+
+### No binary files
+
+ASF source releases must not contain compiled code. Scan for anything that
+isn't text:
+
+```bash
+find apache-airflow-<SDK>-<VERSION>/ -type f \
+  -exec sh -c 'file -b "$1" | grep -qviE "text|json|xml|empty" && echo "$1"' _ 
{} \;
+```
+
+This should print nothing.
+
+### Build from source
+
+**Java.** Regenerate the Gradle wrapper from a locally installed Gradle, then
+build:
+
+```bash
+cd apache-airflow-java-sdk-<VERSION>
+gradle wrapper \
+    --gradle-distribution-url <GRADLE-DISTRIBUTION-URL> \
+    --gradle-distribution-sha256-sum <GRADLE-DISTRIBUTION-SHA>
+./gradlew build
+```
+
+Use values from `distributionUrl` and `distributionSha256Sum` in the bundled
+`gradle/wrapper/gradle-wrapper.properties` to fill in
+`<GRADLE-DISTRIBUTION-URL>` and `<GRADLE-DISTRIBUTION-SHA>`.
+
+Run `gradle wrapper` with that same Gradle version. The task configures
+`buildSrc`, and a different Gradle resolves a `kotlin-dsl` plugin version that
+`verification-metadata.xml` does not pin, so strict verification fails before
+the wrapper is written. If your installed Gradle differs, download the pinned
+distribution, check it against the same SHA-256, and use it directly:
+
+```bash
+curl -LO <GRADLE-DISTRIBUTION-URL>
+echo "<GRADLE-DISTRIBUTION-SHA>  gradle-<GRADLE-VERSION>-bin.zip" | shasum -a 
256 -c
+unzip -q gradle-<GRADLE-VERSION>-bin.zip
+cd apache-airflow-java-sdk-<VERSION>
+../gradle-<GRADLE-VERSION>/bin/gradle build
+```
+
+That Gradle version must also support the JDK it runs on; for example,
+Gradle 8.14 cannot run on JDK 26.
+
+**Go.**
+
+```bash
+cd apache-airflow-go-sdk-<VERSION>
+go build ./...
+go test ./...
+```
+
+**TypeScript.**
+
+```bash
+cd apache-airflow-ts-sdk-<VERSION>
+pnpm install --frozen-lockfile
+pnpm test
+pnpm run build
+pnpm run verify:package
+```
+
+## Verify the release candidate by Contributors
+
+Contributors can check that the release candidate works by using it from a
+throwaway project.
+
+### Java SDK
+
+Resolve the staged Nexus artifacts to confirm they're actually consumable,
+following the same pattern as the "Dry-run against a local repository" step in
+[`java-sdk/DEVELOPMENT.md`](../java-sdk/DEVELOPMENT.md): point a
+`repositories {}` block at the staging repository URL from the vote email,
+declare a dependency on `org.apache.airflow:airflow-sdk-bom:<VERSION>`, and
+confirm the transitive artifacts (including `airflow-sdk-jpl`) resolve and the
+example bundle builds against them.
+
+### Go SDK
+
+The module is fetched straight from the tag:
+
+```bash
+go get github.com/apache/airflow/go-sdk@v<VERSION>-rc<N>
+```
+
+### TypeScript SDK
+
+The release candidate is published on npm under the `rc` dist-tag:
+
+```bash
+npm install @apache-airflow/ts-sdk@<VERSION>-rc<N>
+```
+
+## Check the release candidate commit
+
+The RC tag must point at a commit that is on `main` or on the core release
+branch the SDK is released from (`vX-Y-test` or `vX-Y-stable`). Core release
+branches are occasionally rewritten. A rewrite after the RC is tagged leaves
+the voted commit reachable only through the tag, and the TypeScript release
+workflow then refuses to publish from it.
+
+Run this just before sending the vote email, and again before tagging the final
+release:
+
+```bash
+git fetch upstream
+git merge-base --is-ancestor <rc-commit> upstream/<release-branch> \
+  && echo "OK: on <release-branch>" \
+  || echo "NOT on <release-branch>"
+```
+
+If the check fails before the vote, find the rewritten branch's equivalent
+commit (`git rev-parse <old-commit>:<SDK>` and `git rev-parse 
<new-commit>:<SDK>`
+print the same tree), tag the RC there, and name that commit in the vote email.
+
+## After a successful vote
+
+Reply to the vote thread with a `[RESULT][VOTE]` email once the vote has been
+open for at least 72 hours and has at least three binding +1 votes and more
+binding +1 than -1 votes. List the binding and non-binding votes separately.
+Then follow the steps below. The final tag and the binary publishing differ per
+SDK:
+
+| SDK        | `<SDK-NAME>`     | `<FINAL-TAG>`        | Publish binaries      
                                                                    |
+|------------|------------------|----------------------|-------------------------------------------------------------------------------------------|
+| Java       | `Java SDK`       | `java-sdk/<VERSION>` | [Release the Nexus 
staging repository](../java-sdk/DEVELOPMENT.md#after-a-successful-vote) |
+| Go         | `Go SDK`         | `go-sdk/v<VERSION>`  | [Warm the Go module 
proxy](../go-sdk/DEVELOPMENT.md#after-a-successful-vote)              |
+| TypeScript | `TypeScript SDK` | `ts-sdk/<VERSION>`   | [Publish to 
npm](../ts-sdk/DEVELOPMENT.md#after-a-successful-vote)                        |
+
+### Move the source package to `dist/release`
+
+```bash
+svn mv https://dist.apache.org/repos/dist/dev/airflow/<SDK>/<VERSION>-rc<N> \
+       https://dist.apache.org/repos/dist/release/airflow/<SDK>/<VERSION> \
+       -m "Release Apache Airflow <SDK-NAME> <VERSION>"
+```
+
+Then remove the release this one supersedes. Per the
+[ASF release distribution 
policy](https://infra.apache.org/release-distribution.html#archival),
+`dist/release` should hold the latest release of each line still under
+development, and older ones remain available from `archive.apache.org`.
+Confirm the previous release is on the archive before removing it:
+
+```bash
+curl -fsI 
https://archive.apache.org/dist/airflow/<SDK>/<PREVIOUS-VERSION>/apache-airflow-<SDK>-<PREVIOUS-VERSION>-src.tar.gz
+svn rm 
https://dist.apache.org/repos/dist/release/airflow/<SDK>/<PREVIOUS-VERSION> \
+       -m "Remove superseded Apache Airflow <SDK-NAME> <PREVIOUS-VERSION>"
+```
+
+### Tag the final version
+
+Run the [commit check](#check-the-release-candidate-commit) again, then tag the
+voted commit and push the tag:
+
+```bash
+git tag -s <FINAL-TAG> <voted-commit> -m "Apache Airflow <SDK-NAME> <VERSION>"
+git push upstream <FINAL-TAG>
+```
+
+Keep the RC tag for traceability.
+
+For TypeScript, the voted commit is the one the source package was built from,
+where `package.json` has the plain `<VERSION>`. The vote email names it. The RC
+tag's own commit has `<VERSION>-rc<N>` in `package.json`, so the release
+workflow cannot publish the final version from it.
+
+The "Protect language SDK release tags" ruleset in `.asf.yaml` blocks deleting
+or moving SDK tags for everyone except committers. Get the tag right the first
+time anyway: once the Go module proxy has fetched a tag, it keeps that commit
+forever.
+
+### Publish the binaries
+
+Follow the SDK's own steps linked in the table above.
+
+### Publish a GitHub release
+
+Attach the **voted, signed** source artifacts, exported from `dist/release`
+and verified again:
+
+```bash
+svn export https://dist.apache.org/repos/dist/release/airflow/<SDK>/<VERSION>
+cd <VERSION>
+shasum -a 512 -c apache-airflow-<SDK>-<VERSION>-src.tar.gz.sha512
+gpg --verify apache-airflow-<SDK>-<VERSION>-src.tar.gz.asc \
+    apache-airflow-<SDK>-<VERSION>-src.tar.gz
+
+gh release create <FINAL-TAG> \
+  --repo apache/airflow \
+  --title "Apache Airflow <SDK-NAME> <VERSION>" \
+  --notes "<the Changes since line from the vote email>" \
+  --verify-tag \
+  --latest=false \
+  --prerelease \
+  apache-airflow-<SDK>-<VERSION>-src.tar.gz \
+  apache-airflow-<SDK>-<VERSION>-src.tar.gz.asc \
+  apache-airflow-<SDK>-<VERSION>-src.tar.gz.sha512
+```
+
+Drop the `--prerelease` flag if this is not a prerelease. Keep
+`--latest=false` either way. Otherwise the SDK release replaces Airflow core
+as the repository's *Latest* release.
+
+### Publish the API docs
+
+**Java and TypeScript.** Trigger the *Publish Docs to S3* workflow for the
+final tag:
+
+```bash
+gh workflow run "Publish Docs to S3" --repo apache/airflow --ref main \
+  -f ref=<FINAL-TAG> \
+  -f include-docs=<SDK> \
+  -f destination=live
+```
+
+Optionally use `destination=staging` first to check, then `live`. Each run
+spends about 15 minutes building the CI image before the SDK jobs start. When
+releasing Java and TypeScript together, one run can build both with
+`-f include-docs="java-sdk ts-sdk"`, from any ref where both SDK directories
+match their voted sources.
+
+Confirm that `https://airflow.apache.org/docs/<SDK>/<VERSION>/` resolves.
+`https://airflow.apache.org/docs/<SDK>/stable/` can show the previous version
+in the CDN for a while after publishing.
+
+**Go.** The API docs are on pkg.go.dev, which the Go SDK's publishing step
+covers.
+
+### Announce
+
+Wait until the binaries are available and the docs URL resolves:
+
+* **Java:** Maven Central has synced (the BOM resolves for a fresh consumer).
+  This takes about an hour after the release.
+* **Go:** pkg.go.dev shows the version.
+* **TypeScript:** `npm view @apache-airflow/ts-sdk dist-tags.latest` prints
+  `<VERSION>`.
+
+Then send a plain-text `[ANNOUNCE]` email to `[email protected]`, cc
+`[email protected]`:
+
+```text
+Subject: [ANNOUNCE] Apache Airflow <SDK-NAME> <VERSION> Released
+
+Dear Airflow community,
+
+I'm happy to announce that Apache Airflow <SDK-NAME> <VERSION> was just 
released.
+
+The signed source release can be downloaded from:
+https://downloads.apache.org/airflow/<SDK>/<VERSION>/
+
+<BINARIES>
+
+The API documentation is available at:
+<DOCS-URL>
+
+<Optional: one or two lines on notable changes; omit for the first release.>
+
+Thanks to everyone who contributed to and tested this release.
+
+Cheers,
+<your name>
+```
+
+Fill `<BINARIES>` and `<DOCS-URL>` for the SDK:
+
+* **Java.**
+  `<BINARIES>`: "We also published the convenience binaries to Maven Central,
+  under group id org.apache.airflow. Import airflow-sdk-bom:<VERSION> to keep
+  the module versions aligned."
+  `<DOCS-URL>`: `https://airflow.apache.org/docs/java-sdk/<VERSION>/`
+* **Go.**
+  `<BINARIES>`: "Add it to a Go project with:
+  go get github.com/apache/airflow/go-sdk@v<VERSION>"
+  `<DOCS-URL>`: 
`https://pkg.go.dev/github.com/apache/airflow/go-sdk@v<VERSION>`
+* **TypeScript.**
+  `<BINARIES>`: "We also published the convenience package to npm as
+  @apache-airflow/ts-sdk. Install it with:
+  npm install @apache-airflow/ts-sdk@<VERSION>"
+  `<DOCS-URL>`: `https://airflow.apache.org/docs/ts-sdk/<VERSION>/`
+
+Run `grep '<' email.txt` on the rendered email and confirm **no output**. Any
+match means a placeholder was left unfilled.
+
+### Record the release
+
+Add the release (version and date) in the ASF Committee Report Helper:
+<https://reporter.apache.org/addrelease.html?airflow>. Name it
+`<SDK-NAME> <VERSION>`, for example `Java SDK 1.0.0`, to match earlier entries
+such as `Java SDK 1.0.0-beta1` and `Task SDK x.y.z`.
+
+## If the vote fails
+
+Reply to the vote thread to close it, then:
+
+1. Remove the candidate from `dist/dev`:
+
+   ```bash
+   svn rm https://dist.apache.org/repos/dist/dev/airflow/<SDK>/<VERSION>-rc<N> 
\
+          -m "Remove failed Apache Airflow <SDK-NAME> <VERSION>-rc<N>"
+   ```
+
+2. Undo the SDK-specific publishing, as described under "If the vote fails" in
+   the SDK's `DEVELOPMENT.md`.
+3. Fix the issue and cut the next RC (`<VERSION>-rc<N+1>`). The released 
version
+   stays the same; only the RC counter in the tag increments. Keep the failed
+   RC tag.
diff --git a/go-sdk/DEVELOPMENT.md b/go-sdk/DEVELOPMENT.md
index 7419e3605c7..f73cc795571 100644
--- a/go-sdk/DEVELOPMENT.md
+++ b/go-sdk/DEVELOPMENT.md
@@ -182,6 +182,107 @@ have. 
[`go_native.json`](../airflow-core/tests/unit/dag_processing/lang_sdk_fixt
 holds the Go output for the same Dags, so that the Airflow core tests check 
that Airflow loads it.
 `TestSerializeConformanceDags` says how to rewrite it.
 
+## Calling a release vote
+
+Every release needs a `[VOTE]` on `[email protected]`. The vote is on the
+signed source package in `dist/dev`. Go has no binary artifacts: the module is
+fetched straight from the git tag, so the release candidate is installable for
+testing as soon as `go-sdk/v<VERSION>-rc<N>` is pushed.
+
+Put the signed source package in the dist dev area as
+`go-sdk/<VERSION>-rc<N>/apache-airflow-go-sdk-<VERSION>-src.tar.gz`, with its
+`.asc` signature and `.sha512` checksum.
+
+### Vote email template
+
+```text
+Subject: [VOTE] Release Apache Airflow Go SDK <VERSION> based on 
<VERSION>-rc<N>
+
+Hi,
+
+I would like to call a vote to release Apache Airflow Go SDK <VERSION>, based
+on release candidate <VERSION>-rc<N>.
+
+Changes since <the last release>: <a one-line description>
+
+The release candidate contains the Go module github.com/apache/airflow/go-sdk.
+
+Git information:
+
+- Tag: go-sdk/v<VERSION>-rc<N>
+- Commit: <full-commit-sha>
+- https://github.com/apache/airflow/releases/tag/go-sdk%2Fv<VERSION>-rc<N>
+
+Source release, signatures and checksums:
+https://dist.apache.org/repos/dist/dev/airflow/go-sdk/<VERSION>-rc<N>/
+
+To try the release candidate in a Go project:
+
+    go get github.com/apache/airflow/go-sdk@v<VERSION>-rc<N>
+
+KEYS file (public keys used to sign the release):
+https://downloads.apache.org/airflow/KEYS
+
+Please review and vote. The vote will remain open for at least 72 hours, until 
<YYYY-MM-DD HH:MM UTC>, or until the necessary number of binding votes is 
reached.
+
+[ ] +1 Release this package as Apache Airflow Go SDK <VERSION>
+[ ] +0 No opinion
+[ ] -1 Do not release, because ...
+
+Only votes from Airflow PMC members are binding, but everyone is welcome and 
encouraged to test the release and vote.
+
+The verification process for PMC members and contributors can be found in:
+https://github.com/apache/airflow/blob/main/dev/README_RELEASE_LANGUAGE_SDKS.md#verify-the-release-candidate-by-pmc-members
+https://github.com/apache/airflow/blob/main/dev/README_RELEASE_LANGUAGE_SDKS.md#verify-the-release-candidate-by-contributors
+
+For more details on ASF release verification, see: 
https://www.apache.org/info/verification.html
+
+Best,
+<your name>
+```
+
+Pre-send checklist:
+
+* `go list -m github.com/apache/airflow/go-sdk@v<VERSION>-rc<N>` resolves.
+  Run it only after pushing the RC tag (see the warning in
+  [After a successful vote](#after-a-successful-vote)).
+* `Changes since <the last release>` and the vote deadline are filled in.
+* The RC commit passes the
+  [commit 
check](../dev/README_RELEASE_LANGUAGE_SDKS.md#check-the-release-candidate-commit).
+* Run `grep '<' email.txt` on the rendered email and confirm **no output** —
+  any match means a template placeholder was left unfilled.
+
+### After a successful vote
+
+Follow [After a successful 
vote](../dev/README_RELEASE_LANGUAGE_SDKS.md#after-a-successful-vote)
+in the shared release doc. Go has no binaries to publish. Its "Publish the
+binaries" step is below.
+
+> [!WARNING]
+> Run these steps only after `go-sdk/v<VERSION>` is pushed to `apache/airflow`.
+> Both ask the Go module proxy for the version, and if it doesn't exist yet the
+> proxy caches the "not found" answer. The release then stays unreachable, on
+> the proxy and on pkg.go.dev, for up to an hour after the tag is pushed.
+
+1. **Warm** the module proxy, so the release is fetchable right away and the
+   proxy records the tag's commit:
+
+   ```bash
+   GOPROXY=https://proxy.golang.org go list -m 
github.com/apache/airflow/go-sdk@v<VERSION>
+   ```
+
+   It should print `github.com/apache/airflow/go-sdk v<VERSION>`.
+
+2. **Request** the API docs on pkg.go.dev. Open
+   `https://pkg.go.dev/github.com/apache/airflow/go-sdk@v<VERSION>` and, if the
+   version isn't shown yet, click *Request*. Indexing can take a few minutes.
+
+### If the vote fails
+
+Follow [If the vote 
fails](../dev/README_RELEASE_LANGUAGE_SDKS.md#if-the-vote-fails)
+in the shared release doc. There is nothing Go-specific to undo: the module
+proxy keeps the RC tag, but `go get` only picks a prerelease when asked for it 
by version.
+
 ## Architectural decisions
 
 The [`adr/`](./adr) directory records the design decisions behind the SDK:
diff --git a/java-sdk/DEVELOPMENT.md b/java-sdk/DEVELOPMENT.md
index fdcc1ce4807..a5134c4e312 100644
--- a/java-sdk/DEVELOPMENT.md
+++ b/java-sdk/DEVELOPMENT.md
@@ -280,7 +280,8 @@ is the source-package URL you link in the vote.
 Send a `[VOTE]` email to `[email protected]` linking the git tag and
 commit, the source package in `dist/dev`, the closed Nexus staging repository,
 and the `KEYS` file. See "Vote email template" below for the exact fields to
-fill in, and "Verifying a release" for what to ask reviewers to check.
+fill in, and 
[`dev/README_RELEASE_LANGUAGE_SDKS.md`](../dev/README_RELEASE_LANGUAGE_SDKS.md)
+for what to ask reviewers to check.
 
 ### Vote email template
 
@@ -333,8 +334,9 @@ Please review and vote. The vote will remain open for at 
least 72 hours, until <
 
 Only votes from Airflow PMC members are binding, but everyone is welcome and 
encouraged to test the release and vote.
 
-The verification process can be found in the main repository:
-https://github.com/apache/airflow/tree/java-sdk/<VERSION>-rc<N>/java-sdk#verifying-a-release
+The verification process for PMC members and contributors can be found in:
+https://github.com/apache/airflow/blob/main/dev/README_RELEASE_LANGUAGE_SDKS.md#verify-the-release-candidate-by-pmc-members
+https://github.com/apache/airflow/blob/main/dev/README_RELEASE_LANGUAGE_SDKS.md#verify-the-release-candidate-by-contributors
 
 For more details on ASF release verification, see: 
https://www.apache.org/info/verification.html
 
@@ -354,115 +356,21 @@ Pre-send checklist:
   date -u -v+72H '+%Y-%m-%d %H:%M UTC'          # BSD date (macOS)
   ```
 
+* The RC commit passes the
+  [commit 
check](../dev/README_RELEASE_LANGUAGE_SDKS.md#check-the-release-candidate-commit).
 * Run `grep '<' email.txt` on the rendered email and confirm **no output** —
   any match means a template placeholder (`<N>`, `<NNNN>`, `<YYYY-MM-DD ...>`,
   etc.) was left unfilled.
 
 ### Verifying a release
 
-Anyone on `[email protected]` can (and should) independently verify a
-candidate before voting. Below is the checklist a reviewer — or the release
-manager, before sending the vote — should run against the source package in
-`dist/dev`.
-
-1. **Checksum.** Confirm the published SHA-512 matches the downloaded tarball:
-
-   ```bash
-   shasum -a 512 -c apache-airflow-java-sdk-<VERSION>-src.tar.gz.sha512
-   ```
-
-   `shasum` ships with both macOS and most Linux distributions; `sha512sum -c`
-   works too on Linux but is not installed on macOS by default.
-
-2. **Signature.** Import the `KEYS` file and verify the GPG signature:
-
-   ```bash
-   curl -O https://downloads.apache.org/airflow/KEYS
-   gpg --import KEYS
-   gpg --verify apache-airflow-java-sdk-<VERSION>-src.tar.gz.asc \
-       apache-airflow-java-sdk-<VERSION>-src.tar.gz
-   ```
-
-3. **Diff against the git tag.** Extract the tarball and compare it with a
-   clean checkout of the tag it claims to be built from. They should be
-   identical except for the files kept out of the source release via
-   `.gitattributes` `export-ignore`. The extracted top-level directory should 
be
-   `apache-airflow-java-sdk-<version>` without the `-src` suffix that only
-   appears in the tarball's own filename:
-
-   ```bash
-   tar xzf apache-airflow-java-sdk-<VERSION>-src.tar.gz
-   git clone --branch java-sdk/<VERSION>-rc<N> \
-     https://github.com/apache/airflow.git tag-checkout
-   diff -rq apache-airflow-java-sdk-<VERSION>/ tag-checkout/java-sdk/ \
-     | grep -vE ': (gradlew|gradlew\.bat|gradle-wrapper\.jar|scripts)$'
-   ```
-
-   Any remaining diff output is unexpected and should block the vote.
-
-   If the vote email says the source package was built from a commit before the
-   tag, diff the tarball against that commit instead, then confirm the tag adds
-   nothing to the SDK directory except the version bump. Limit the diff to the
-   SDK directory; the tag usually sits on a release branch, so an unscoped diff
-   also lists unrelated commits that landed in between:
-
-   ```bash
-   git -C tag-checkout diff <SOURCE-COMMIT> java-sdk/<VERSION>-rc<N> --stat -- 
java-sdk/
-   ```
-
-4. **No binary files.** ASF source releases must not contain compiled code.
-   Scan for anything that isn't text:
-
-   ```bash
-   find apache-airflow-java-sdk-<VERSION>/ -type f \
-     -exec sh -c 'file -b "$1" | grep -qviE "text|json|xml|empty" && echo 
"$1"' _ {} \;
-   ```
-
-   This should print nothing.
-
-5. **Build from source.** Regenerate the Gradle wrapper from a locally 
installed
-   Gradle (see the *Upload the source package* section above):
-
-   ```bash
-   cd apache-airflow-java-sdk-<VERSION>
-   gradle wrapper \
-       --gradle-distribution-url <GRADLE-DISTRIBUTION-URL> \
-       --gradle-distribution-sha256-sum <GRADLE-DISTRIBUTION-SHA>
-   ./gradlew build
-   ```
-
-   Use values from `distributionUrl` and `distributionSha256Sum` in the bundled
-   `gradle/wrapper/gradle-wrapper.properties` to fill in
-   `<GRADLE-DISTRIBUTION-URL>` and `<GRADLE-DISTRIBUTION-SHA>`.
-
-   Run `gradle wrapper` with that same Gradle version. The task configures
-   `buildSrc`, and a different Gradle resolves a `kotlin-dsl` plugin version 
that
-   `verification-metadata.xml` does not pin, so strict verification fails 
before
-   the wrapper is written. If your installed Gradle differs, download the 
pinned
-   distribution, check it against the same SHA-256, and use it directly:
-
-   ```bash
-   curl -LO <GRADLE-DISTRIBUTION-URL>
-   echo "<GRADLE-DISTRIBUTION-SHA>  gradle-<GRADLE-VERSION>-bin.zip" | shasum 
-a 256 -c
-   unzip -q gradle-<GRADLE-VERSION>-bin.zip
-   cd apache-airflow-java-sdk-<VERSION>
-   ../gradle-<GRADLE-VERSION>/bin/gradle build
-   ```
-
-   That Gradle version must also support the JDK it runs on; for example,
-   Gradle 8.14 cannot run on JDK 26.
-
-6. **Staged-binary smoke test.** Resolve the staged Nexus artifacts from a
-   throwaway project to confirm they're actually consumable, following the
-   same pattern as the "Dry-run against a local repository" step: point a
-   `repositories {}` block at the staging repository URL, declare a dependency
-   on `org.apache.airflow:airflow-sdk-bom:<VERSION>`, and confirm the
-   transitive artifacts (including `airflow-sdk-jpl`) resolve and the example
-   bundle builds against them.
+The reviewer checklist for all language SDKs is in
+[`dev/README_RELEASE_LANGUAGE_SDKS.md`](../dev/README_RELEASE_LANGUAGE_SDKS.md#verify-the-release-candidate-by-pmc-members).
 
 ### After a successful vote
 
-Reply with a `[RESULT][VOTE]` tally, then:
+Follow [After a successful 
vote](../dev/README_RELEASE_LANGUAGE_SDKS.md#after-a-successful-vote)
+in the shared release doc. Its "Publish the binaries" step for Java is:
 
 1. **Release** the staging repository so the artifacts sync to Maven Central
    (a few hours). Nothing is rebuilt or re-signed.
@@ -505,149 +413,10 @@ Reply with a `[RESULT][VOTE]` tally, then:
 
    Then select the repository in the Nexus UI and click *Drop*.
 
-3. **Move** the source package from `dist/dev` to `dist/release`:
-
-   ```bash
-   svn mv 
https://dist.apache.org/repos/dist/dev/airflow/java-sdk/<VERSION>-rc<N> \
-          
https://dist.apache.org/repos/dist/release/airflow/java-sdk/<VERSION> \
-          -m "Release Apache Airflow Java SDK <VERSION>"
-   ```
-
-   Then remove the release this one supersedes. Per the
-   [ASF release distribution 
policy](https://infra.apache.org/release-distribution.html#archival),
-   `dist/release` should hold the latest release of each line still under
-   development, and older ones remain available from `archive.apache.org`. 
Confirm the previous release is on the
-   archive before removing it:
-
-   ```bash
-   curl -fsI 
https://archive.apache.org/dist/airflow/java-sdk/<PREVIOUS-VERSION>/apache-airflow-java-sdk-<PREVIOUS-VERSION>-src.tar.gz
-   svn rm 
https://dist.apache.org/repos/dist/release/airflow/java-sdk/<PREVIOUS-VERSION> \
-          -m "Remove superseded Apache Airflow Java SDK <PREVIOUS-VERSION>"
-   ```
-
-4. **Tag** the final version on the same commit that was voted:
-
-   ```bash
-   git tag -s java-sdk/<VERSION> <voted-commit-hash> -m "Apache Airflow Java 
SDK <VERSION>"
-   git push upstream java-sdk/<VERSION>
-   ```
-
-   Keep the RC tag for traceability.
-
-   Release branches are occasionally rewritten, which can leave the voted
-   commit reachable only through the RC tag. That does not block the Java
-   release, but check it so you can mention it in the GitHub release if
-   needed:
-
-   ```bash
-   git fetch upstream
-   git merge-base --is-ancestor <voted-commit-hash> upstream/<release-branch> \
-     || echo "Voted commit is not on <release-branch>"
-   ```
-
-5. Publish a **GitHub release**. Attach the **voted, signed** source artifacts,
-   exported from `dist/release` and verified again:
-
-   ```bash
-   svn export 
https://dist.apache.org/repos/dist/release/airflow/java-sdk/<VERSION>
-   cd <VERSION>
-   shasum -a 512 -c apache-airflow-java-sdk-<VERSION>-src.tar.gz.sha512
-   gpg --verify apache-airflow-java-sdk-<VERSION>-src.tar.gz.asc \
-       apache-airflow-java-sdk-<VERSION>-src.tar.gz
-
-   gh release create java-sdk/<VERSION> \
-     --repo apache/airflow \
-     --title "Apache Airflow Java SDK <VERSION>" \
-     --notes "<the Changes since line from the vote email>" \
-     --verify-tag \
-     --latest=false \
-     --prerelease \
-     apache-airflow-java-sdk-<VERSION>-src.tar.gz \
-     apache-airflow-java-sdk-<VERSION>-src.tar.gz.asc \
-     apache-airflow-java-sdk-<VERSION>-src.tar.gz.sha512
-   ```
-
-   Drop the `--prerelease` flag if this is not a prerelease. Keep
-   `--latest=false` either way. Otherwise the SDK release replaces Airflow core
-   as the repository's *Latest* release.
-
-6. Publish the **API docs.** Trigger the *Publish Docs to S3* workflow in
-   `apache/airflow` for the release tag:
-
-   ```bash
-   gh workflow run "Publish Docs to S3" --repo apache/airflow --ref main \
-     -f ref=java-sdk/<VERSION> \
-     -f include-docs=java-sdk \
-     -f destination=live
-   ```
-
-   Optionally use `destination=staging` first to check, then `live`. It may be
-   possible to `auto` instead, which resolves to `live` for a release tag.
-
-   Each run spends about 15 minutes building the CI image before the SDK jobs
-   start. If you are releasing the TypeScript SDK at the same time, one run can
-   build both with `-f include-docs="java-sdk ts-sdk"`, from any ref where both
-   SDK directories match their voted sources.
-
-   Confirm that `https://airflow.apache.org/docs/java-sdk/<VERSION>/` resolves.
-   `https://airflow.apache.org/docs/java-sdk/stable/` and the `/docs/java-sdk/`
-   redirect to it can show the previous version in the CDN for a while after
-   publishing.
-
-7. **Announce.** Wait ~1 hour after promoting so Maven Central has synced, then
-   send a plain-text `[ANNOUNCE]` email to `[email protected]` (cc
-   `[email protected]`) using the "Announce email template" below.
-
-8. **Record** the release (version and date) in the ASF Committee Report
-   Helper: <https://reporter.apache.org/addrelease.html?airflow>. Name it
-   `Java SDK <VERSION>`, for example `Java SDK 1.0.0`, to match earlier entries
-   such as `Java SDK 1.0.0-beta1` and `Task SDK x.y.z`. The other language SDKs
-   use the same pattern (`TypeScript SDK <VERSION>`, `Go SDK <VERSION>`).
-
-### Announce email template
-
-Send to `[email protected]`, cc `[email protected]`.
-
-```text
-Subject: [ANNOUNCE] Apache Airflow Java SDK <VERSION> Released
-
-Dear Airflow community,
-
-I'm happy to announce that Apache Airflow Java SDK <VERSION> was just released.
-
-The signed source release can be downloaded from:
-https://downloads.apache.org/airflow/java-sdk/<VERSION>/
-
-We also published the convenience binaries to Maven Central, under group id
-org.apache.airflow. Import airflow-sdk-bom:<VERSION> to keep the module 
versions
-aligned.
-
-The API documentation is available at:
-https://airflow.apache.org/docs/java-sdk/<VERSION>/
-
-<Optional: one or two lines on notable changes; omit for the first release.>
-
-Thanks to everyone who contributed to and tested this release.
-
-Cheers,
-<your name>
-```
-
-Pre-send checklist:
-
-* The Maven Central sync has completed (the BOM resolves for a fresh consumer)
-  and the docs URL above resolves.
-* Fill or delete the optional changes line.
-* Run `grep '<' email.txt` on the rendered email and confirm **no output** --
-  any match means a placeholder (`<VERSION>`, `<your name>`, ...) was left
-  unfilled.
-
-
 ### If the vote fails
 
-Close the vote, **drop** the staging repository in Nexus, remove the `dist/dev`
-candidate, fix the issue, and cut the next RC (`...-rc2`). The released version
-stays the same (e.g. `<VERSION>`); only the RC counter in the tag increments.
+Follow [If the vote 
fails](../dev/README_RELEASE_LANGUAGE_SDKS.md#if-the-vote-fails)
+in the shared release doc. For Java, also **drop** the staging repository in 
Nexus.
 
 ## Contributing
 
diff --git a/ts-sdk/DEVELOPMENT.md b/ts-sdk/DEVELOPMENT.md
index 432a331c70e..41b20924735 100644
--- a/ts-sdk/DEVELOPMENT.md
+++ b/ts-sdk/DEVELOPMENT.md
@@ -137,9 +137,9 @@ with `npm trust revoke` first.
 Because the registry cannot express "stage only" and "publish only" as separate
 relationships, what separates the two paths is the GitHub environment gate
 rather than an npm-side permission split. Require reviewers and prevent
-self-review on `ts-sdk-npm-release`, restrict its deployment tags to
-`ts-sdk/*`, and protect those tags from updates and deletion with a repository
-ruleset. The pinned `--environment` claim means a workflow edit that drops the
+self-review on `ts-sdk-npm-release`, and restrict its deployment tags to
+`ts-sdk/*`. The "Protect language SDK release tags" ruleset in `.asf.yaml`
+keeps those tags from being updated or deleted by anyone but committers. The 
pinned `--environment` claim means a workflow edit that drops the
 gate loses the ability to publish at all.
 
 Create and push a `ts-sdk/<version>` tag whose version exactly matches
@@ -202,3 +202,115 @@ in the order they were requested so the dist-tag does not 
regress. Both
 publication paths use short-lived npm OIDC credentials and automatically
 publish provenance. After verifying the trusted-publisher setup, disable
 token-based publishing and revoke obsolete npm automation tokens.
+
+## Calling a release vote
+
+Every release needs a `[VOTE]` on `[email protected]`. The vote is
+formally on the signed source package in `dist/dev`; the npm package is the
+convenience binary.
+
+The release candidate is tagged `ts-sdk/<VERSION>-rc<N>` with `package.json`
+set to the same `<VERSION>-rc<N>`, then published with the `formal` workflow
+above using the `rc` dist-tag, so reviewers can install it with `npm install`.
+
+Put the signed source package in the dist dev area as
+`ts-sdk/<VERSION>-rc<N>/apache-airflow-ts-sdk-<VERSION>-src.tar.gz`, with its
+`.asc` signature and `.sha512` checksum.
+
+### Vote email template
+
+```text
+Subject: [VOTE] Release Apache Airflow TypeScript SDK <VERSION> based on 
<VERSION>-rc<N>
+
+Hi,
+
+I would like to call a vote to release Apache Airflow TypeScript SDK <VERSION>,
+based on release candidate <VERSION>-rc<N>.
+
+Changes since <the last release>: <a one-line description>
+
+The release candidate contains the following npm package:
+
+- @apache-airflow/ts-sdk
+
+Git information:
+
+- Tag: ts-sdk/<VERSION>-rc<N>
+- Commit: <full-commit-sha>
+- https://github.com/apache/airflow/releases/tag/ts-sdk%2F<VERSION>-rc<N>
+
+Source release, signatures and checksums:
+https://dist.apache.org/repos/dist/dev/airflow/ts-sdk/<VERSION>-rc<N>/
+
+Convenience binary (published on npm under the rc dist-tag):
+https://www.npmjs.com/package/@apache-airflow/ts-sdk/v/<VERSION>-rc<N>
+
+To try the release candidate in a project:
+
+    npm install @apache-airflow/ts-sdk@<VERSION>-rc<N>
+
+KEYS file (public keys used to sign the release):
+https://downloads.apache.org/airflow/KEYS
+
+Please review and vote. The vote will remain open for at least 72 hours, until 
<YYYY-MM-DD HH:MM UTC>, or until the necessary number of binding votes is 
reached.
+
+[ ] +1 Release this package as Apache Airflow TypeScript SDK <VERSION>
+[ ] +0 No opinion
+[ ] -1 Do not release, because ...
+
+Only votes from Airflow PMC members are binding, but everyone is welcome and 
encouraged to test the release and vote.
+
+The verification process for PMC members and contributors can be found in:
+https://github.com/apache/airflow/blob/main/dev/README_RELEASE_LANGUAGE_SDKS.md#verify-the-release-candidate-by-pmc-members
+https://github.com/apache/airflow/blob/main/dev/README_RELEASE_LANGUAGE_SDKS.md#verify-the-release-candidate-by-contributors
+
+For more details on ASF release verification, see: 
https://www.apache.org/info/verification.html
+
+Best,
+<your name>
+```
+
+Pre-send checklist:
+
+* `npm view @apache-airflow/ts-sdk@<VERSION>-rc<N> version` prints
+  `<VERSION>-rc<N>`.
+* `Changes since <the last release>` and the vote deadline are filled in.
+* The RC commit passes the
+  [commit 
check](../dev/README_RELEASE_LANGUAGE_SDKS.md#check-the-release-candidate-commit).
+* Run `grep '<' email.txt` on the rendered email and confirm **no output** —
+  any match means a template placeholder was left unfilled.
+
+### After a successful vote
+
+Follow [After a successful 
vote](../dev/README_RELEASE_LANGUAGE_SDKS.md#after-a-successful-vote)
+in the shared release doc. Its "Publish the binaries" step for TypeScript is:
+
+1. **Publish** the final tag to npm with the formal path on the `latest`
+   dist-tag (or the prerelease channel, for a prerelease):
+
+   ```bash
+   gh workflow run ts-sdk-release.yml --repo apache/airflow --ref 
ts-sdk/<VERSION> \
+     -f release_type=formal \
+     -f tag=ts-sdk/<VERSION> \
+     -f npm_tag=latest
+   ```
+
+   Approve the `ts-sdk-npm-release` deployment when the workflow asks for it.
+
+2. **Remove** the `rc` dist-tag, which still points at the last candidate.
+   This needs a maintainer's npm 2FA:
+
+   ```bash
+   npm dist-tag rm @apache-airflow/ts-sdk rc
+   npm view @apache-airflow/ts-sdk dist-tags
+   ```
+
+### If the vote fails
+
+Follow [If the vote 
fails](../dev/README_RELEASE_LANGUAGE_SDKS.md#if-the-vote-fails)
+in the shared release doc. For TypeScript, also deprecate the candidate on
+npm so nobody keeps using it:
+
+```bash
+npm deprecate @apache-airflow/ts-sdk@<VERSION>-rc<N> "Release vote failed; use 
a later release candidate"
+```

Reply via email to