Protocol 28 GA: core 28.0.0 + SDK P28

[Shaptic]

Part of the Protocol 28 GA release train (stellar/go-stellar-sdk#5967).

• Core pins → 28.0.0-3486.2332980a1.noble (deb verified present in apt noble unstable; both env vars kept matching per RELEASE.md)
• go-stellar-sdk → v0.6.1-0.20260803175255-2b16db0ecd45 (the P28 GA merge commit; re-pins to v0.7.0 before this merges to main, once the SDK release is cut)
• Load-test backend adapted to the SDK's multi-bundle LedgersFilePaths API (go-stellar-sdk#5959) — one-element slice, same behavior
• CHANGELOG v28.0.0 section

Not touched (needs a maintainer decision, tracked on the train issue): GALEXIE_INTEGRATION_TESTS_QUICKSTART_IMAGE is still stellar/quickstart:pr799-future, stale since P24.

🤖 Generated with Claude Code

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	github.com/​stellar/​go-stellar-sdk@​v0.6.0 ⏵ v0.7.0	+1

View full report

[Shaptic]

CI failure root-caused: the stale stellar/quickstart:pr799-future pin (a P24-era PR build) can't host a network the GA 28.0.0 captive core will join — Error fast-forwarding to 2: stellar core exited unexpectedly in TestAppendUnbounded. None of quickstart's maintained tracks bundle core 28 yet (auto-update follows apt stable; core 28 hasn't been promoted), so this pins v649-b1276.1-future — the immutable, digest-identical twin of today's quickstart:future, whose core (27.1.0-68-gc1075639) is a direct ancestor of the 28.0.0 GA commit (0 ahead / 31 behind) and protocol-28-capable. Tracked follow-up: re-pin to the stable track once quickstart bundles 28.0.0 GA.