Skip to main content

Download

tip

Seata Go v2.0.0 is the current stable release, covering AT, TCC, and XA modes with registry options for file, Nacos, and Etcd.

System Requirements

ItemRequirement / Notes
Go toolchainGo 1.20 or newer with modules enabled (go env GOPATH configured)
Seata ServerSeata Server 2.5.0+ reachable from your services (HTTP/2 enabled by default in 2.5.0)
Registry / ConfigFile, Nacos, or Etcd v3 registry; optional config center via file or Nacos
DatabaseMySQL 5.7/8.0 for AT & XA; Oracle supported through go-ora (XA)
Operating systemLinux, macOS, Windows (amd64/arm64)

Stable Version

VersionSourceBinaryRelease NotesReference Docs
2.0.0apache-seata-go-2.0.0-incubating-src.tar.gz ASC SHA512apache-seata-go-2.0.0-incubating-bin.tar.gz ASC SHA512v2.0.0 changelogSamples & docs
  1. For upgrade guidance, follow the project README and keep module dependencies in sync with Seata Server.
  2. Older releases are available from the Seata Go archive.

Install via Go Modules

  • (Optional) Pin a proxy for faster downloads: go env -w GOPROXY=https://goproxy.cn,direct.
  • Add the SDK to your module: go get seata.apache.org/seata-go@v2.0.0 (records to go.mod / go.sum).
  • Lock the dependency explicitly by keeping require seata.apache.org/seata-go v2.0.0 and running go mod tidy.
  • Verify dependency integrity before committing: go list seata.apache.org/seata-go/....

Verify the releases

It is crucial to verify the integrity of downloaded artifacts using GPG signatures or SHA checksums. Download the KEYS, .asc, and .sha512 files directly from the Apache distribution directory rather than mirrors.

Verify Signatures

  1. Download the signatures KEYS and the desired release files with their .asc signatures.
  2. Import the public keys:
    gpg --import KEYS
  3. Validate each artifact, for example:
    gpg --verify apache-seata-go-2.0.0-incubating-src.tar.gz.asc apache-seata-go-2.0.0-incubating-src.tar.gz
    gpg --verify apache-seata-go-2.0.0-incubating-bin.tar.gz.asc apache-seata-go-2.0.0-incubating-bin.tar.gz
    A result similar to the following indicates a valid signature:
    gpg: Signature made Tue Apr 29 12:11:09 2025 CST
    gpg: using RSA key 775377BF271D659E591249CD63E269707E8BF0FB
    gpg: Good signature from "xxx" [ultimate]

Verify Checksums

  1. Download the .sha512 file corresponding to the artifact.
  2. Run the checksum validation:
    shasum -c apache-seata-go-2.0.0-incubating-src.tar.gz.sha512
    shasum -c apache-seata-go-2.0.0-incubating-bin.tar.gz.sha512
    Output ending with OK confirms the archive is intact.

Additional Resources