Refresh stellar-cli 26.0.0

[github-actions]

What

Stage a refresh for stellar-cli 26.0.0. builds.json is left unchanged — this carries an empty commit to re-trigger the publish flow for the pairs already declared for this cli.

Why

Triggered by @fnando in https://github.com/stellar/stellar-cli-docker/actions/runs/33014259717.

What is next

See RELEASE.md for the full release process.

This branch carries an empty commit and intentionally leaves builds.json unchanged; push further changes to release/v26.0.0-0 only if this release needs them.

When this PR is reviewed and merged, create a GitHub Release by going to:

https://github.com/stellar/stellar-cli-docker/releases/new?tag=v26.0.0-0&title=26.0.0-0&target=main

The publish workflow fires on the release-published event and:

• Builds and pushes per-arch images for every declared (cli, rust base) pair; tags are mutable, so an existing tag is overwritten in place
• Generates SLSA build provenance + SPDX SBOM attestations on each built image (buildx-native + GitHub-native chains)
• Re-points the :26.0.0 and (if newest) :latest aliases, and mints the immutable :26.0.0-rust<key>-<arch>-N per-arch snapshots for this iteration
• Attaches the SBOM and provenance files to the new GitHub Release, with per-arch digests in the body

[Copilot]

Copilot wasn't able to review any files in this pull request.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.