Protocol 28 GA release train

[Shaptic]

Tracking issue for the Protocol 28 GA release train across go-stellar-sdk, stellar-rpc,
stellar-horizon, and stellar-galexie. Driven by the /release-train skill; the yaml block
below is the machine-readable source of truth and is reconciled against live GitHub state on
every invocation. Humans: check items off, but the yaml is what the skill trusts.

Checklist

• SDK flip PR (protocol-next): Protocol 28 GA: pin stellar-xdr 9c9c1459, clear XDR_FEATURES #5968 — XDR_COMMIT → 9c9c1459, XDR_FEATURES → empty, regen (awaiting review)
• SDK merge PR: Protocol 28 Support #5969 — protocol-next → main (merge commit; awaiting review)
• release sdk: tag v0.7.0 + GitHub release
• rpc: closed stale automation PRs Bump current version of soroban-env to latest tip stellar-rpc#763 / Bump current version of soroban-env to latest tip stellar-rpc#901
• rpc flip PR — crates.io 28.0.0 published ✅; opens once SDK merge commit exists (core docker images still pending for CI)
• rpc merge PR → release rpc (staged: release branch → Jenkins → staging → tag → deploy)
• horizon flip PR — shape reconciliation DONE (main merged into protocol-next 2026-07-31, callable layout + P28 pins in place; core_docker_img typo fixed). Remaining: bump verify-range STELLAR_CORE_VERSION (still 27.1.0 noble), SDK pin, horizon-release.yml #horizon-v fix, CHANGELOG
• horizon merge (gated on a protocol-28 rpc image; 28.0.0-vnext-unstable-195 already exists) → release horizon
• galexie flip PR (debs verified; unblocked)
• galexie merge → wait sha image → release galexie
• re-sync protocol-next in all four repos
• follow-ups: horizon GA rpc-image re-pin; galexie quickstart:pr799-future decision

State

train:
  protocol: 28
  opened: 2026-07-31
stellar_xdr:
  ref: 9c9c145953e80990d6ff1ae3a6a973a0ce6d0694
  commit: 9c9c145953e80990d6ff1ae3a6a973a0ce6d0694
  tag_pending: true            # v28.0 not published yet; verify pin==tag before release sdk
core:
  build: 28.0.0-3486.2332980a1
  verified_flavors: [jammy-deb, jammy~buildtests-deb, noble-deb, noble~buildtests-deb]
  docker_published: false      # stellar/stellar-core jammy+noble both 404 as of 2026-07-31
  xdr_submodule_ok: true       # src/protocol-curr/xdr @ 2332980a1 == 9c9c1459
env_host:
  crates_version: 28.0.0
  tag_released: true           # v28.0.0 tagged 2026-07-31; commit VERIFIED == core p28 submodule
  crates_published: true       # verified on crates.io 2026-07-31 — rpc Cargo flip unblocked
  rs_commit: ba37ea5f76a10710835992fb90f9ec7a14eca499
gates:
  cap_features:
    - {cap: CAP-0083, decision: ship, note: ungated upstream at 9c9c1459}
    - {cap: CAP-0085, decision: ship, note: ungated upstream at 9c9c1459}
    - {cap: CAP-0084, decision: not-in-p28, note: keep CAP_0084_MUXED_CONTRACT gated, no flag anywhere}
sdk:
  next_version: v0.7.0
  flip_pr: 5968                  # MERGED into protocol-next
  merge_pr: 5969                 # open, awaiting review
  merge_sha: null
  released: false
rpc:
  automation_prs_to_close: [763, 901]
  flip_pr: null
  merge_pr: null
  merge_sha: null
  release_pr: null
  rc_deb_build: null
  kube_staging_pr: null
  staging_validated: false
  release_sha: null
  released: false
  ga_deb_build: null
  promoted_stable: false
  kube_dev_pr: null
  kube_prd_pr: null
  ga_image: null
horizon:
  flip_pr: null
  workflow_shape_divergence: false  # resolved 2026-07-31: main (callable jobs, stellar-horizon#202) merged into protocol-next with P28 pins
  broken_core_docker_pin: false     # was 'stellar/stellar-core:.jammy'; fixed on protocol-next 2026-07-31, verified 28.0.0-3486.2332980a1.jammy
  rpc_image_pinned: "stellar/stellar-rpc:28.0.0-vnext-unstable-195"  # already on protocol-next
  merge_pr: null
  merge_sha: null
  released: false
  ga_repin_pr: null
galexie:
  flip_pr: null
  merge_pr: null
  merge_sha: null
  sha_image_published: false
  released: false
resync:
  sdk: false
  rpc: false
  horizon: false
  galexie: false
followups:
  - {repo: stellar-galexie, note: "GALEXIE_INTEGRATION_TESTS_QUICKSTART_IMAGE is stellar/quickstart:pr799-future (stale since P24) — needs a decision"}
  - {repo: stellar-horizon, note: "horizon-release.yml strips #horizon-v from tag names (no-op on vN tags) — fix goes into the flip PR"}

[Shaptic]

rs-soroban-env v28.0.0 tagged — commit ba37ea5f verified identical to stellar-core 28.0.0's src/rust/soroban/p28 submodule (the env-host/core cost-model coherence check passes). Still pending before the rpc flip: soroban-env-host + soroban-simulation 28.0.0 on crates.io, and the stellar/stellar-core docker images for 28.0.0-3486.2332980a1.

[Shaptic]

SDK flip PR opened: #5968 (protocol-next). Generated diff is cosmetic-only; build + xdr tests green locally (one pre-existing ingest flake noted in the PR). Also closed stale stellar-rpc automation PRs stellar/stellar-rpc#763 and stellar/stellar-rpc#901 ahead of the rpc flip.

[Shaptic]

Horizon update: main was merged into protocol-next (callable workflow layout from stellar-horizon#202 now present) with P28 CI refs bumped — deb pin and rpc image (stellar/stellar-rpc:28.0.0-vnext-unstable-195) look correct. One issue spotted: the P28 leg's core_docker_img is malformed ('stellar/stellar-core:.jammy', build string missing) — will be fixed in the horizon flip PR along with verify-range (still 27.1.0.noble), the SDK pin, the horizon-release.yml version-strip fix, and CHANGELOG. Cross-repo issue refs in this body now use the owner/repo#N form.

[Shaptic]

Progress: flip PR #5968 merged (thanks for the review). main merged back into protocol-next (e5d0cb9 — CHANGELOG union, views regenerated with the #5951 generator over P28 XDR, tests green). SDK merge PR opened: #5969 (protocol-next → main, needs review; merge-commit please). crates.io soroban-env-host/soroban-simulation 28.0.0 verified published — rpc's Cargo flip is unblocked once the SDK merge commit exists. Still waiting on stellar/stellar-core docker images for 28.0.0-3486.2332980a1.