Bump version to 26.0.0

[github-actions]

What

Bump version to 26.0.0, creating release branch.

Why

Triggered by @mootz12 in https://github.com/stellar/rs-soroban-sdk/actions/runs/25447098551.

What is next

See the release instructions for a full rundown on the release process:
https://github.com/stellar/actions/blob/main/README-rust-release.md

Commit any changes to the release/v26.0.0 branch that are needed in this release.

If this is a regular release releasing from main, merge this PR when ready, and after merging, create a release for this version by going to this link: https://github.com/stellar/rs-soroban-sdk/releases/new?tag=v26.0.0&title=26.0.0

If this is a backport or patch release of a past version, see the release instructions. When ready to release this branch create a release by going to this link:
https://github.com/stellar/rs-soroban-sdk/releases/new?tag=v26.0.0&title=26.0.0&target=release/v26.0.0

[claude]

Claude finished @mootz12's task in 59s —— View job

---

PR Review — Bump version to 26.0.0

This is an automated release-prep PR generated by the standard stellar/actions rust-release workflow. The changes are purely mechanical version-string updates with no behavior changes.

Summary of changes

• Cargo.toml: workspace version and the 9 path-based workspace.dependencies entries flipped from 26.0.0-rc.1 → 26.0.0.
• Cargo.lock: corresponding version fields updated for the 9 workspace crates plus internal test crates (proc_macros, test_account).
• tests/fuzz/fuzz/Cargo.lock: same bump for the fuzz workspace's view of those crates.

Verification

• All 9 workspace crates (soroban-sdk, soroban-sdk-macros, soroban-meta, soroban-spec, soroban-spec-rust, soroban-ledger-snapshot, soroban-token-sdk, soroban-token-spec, stellar-asset-spec) are bumped consistently in Cargo.toml.
• No stale 26.0.0-rc.1 / rc.0 strings remain (grep -rn "26.0.0-rc" --include="*.toml" --include="*.lock" --include="*.md" --include="*.rs" returns nothing).
• Both lockfiles (Cargo.lock, tests/fuzz/fuzz/Cargo.lock) reflect the same 26.0.0 version, so a fresh build won't re-introduce the rc string.
• External pinned deps untouched and intentional: soroban-env-common/guest/host = =26.1.3, stellar-strkey = =0.0.16, stellar-xdr = =26.0.1 — these track the env/xdr release cadence and are correctly left alone for this SDK bump.
• rust-version = "1.91.0" unchanged.
• git diff origin/main...HEAD --stat is symmetric (70/70), consistent with a pure version-string flip.

Findings

Code quality / best practices — None. Mechanical bump, no logic changes.

Potential bugs — None. The lockfile and manifest are in sync; cargo will not regenerate the lockfile on first build.

Security — None. No new dependencies introduced and no version downgrades. External pinned versions (= requirements on env/xdr) preserved, so supply-chain surface is unchanged.

Performance — N/A.

Release-process notes (informational)

• Per the PR body, after merge the release should be cut at https://github.com/stellar/rs-soroban-sdk/releases/new?tag=v26.0.0&title=26.0.0
• Worth confirming before merge that the CI matrix (especially the wasm32v1-none build and the fuzz workspace check) is green on this branch — the version bump itself can't break things, but a clean signal on the release branch is the right gate.

Verdict

LGTM — this is a routine -rc.1 → final release bump. Approve and merge once CI is green.

---

• Read changed files (Cargo.toml, Cargo.lock, tests/fuzz/fuzz/Cargo.lock)
• Verify version bumps are consistent across files
• Sweep for stale rc strings
• Confirm external pinned deps untouched
• Post review
  • Branch: release/v26.0.0