Comparing changes

### What Add an `--only-commit` flag to `stellar version` that prints just the commit sha of the build, alongside the existing `--only-version` and `--only-version-major` flags. ### Why The commit sha is already embedded in the build and shown as part of the full version output, but there is no way to extract it on its own. A dedicated flag makes the commit sha consumable by scripts and tooling without needing to parse the multi-line full version output. ### Known limitations N/A

### What Delete .github/workflows/claude-review.yml. ### Why It needs some iteration. Fires too frequently. It's noisy and too verbose. There's no way to silence it on long iterative PRs. And we should iterate on the pull request target usage as well. In the interim we've enabled Codex review, which does not have many of these downsides by default. The shared claude-review workflow we can keep iterating on, and test it on one repo before bringing it to a bunch and creating too much noise: - stellar/actions#103

…arch manifest (#2605)

## What Make the `stellar/stellar-cli` install action resilient to transient network failures by adding retries to its two network-dependent steps: - **Binary download:** the `curl` call now retries up to 5 times with backoff (`--retry 5 --retry-delay 5 --retry-connrefused --retry-all-errors`), bounded by `--connect-timeout 30` and `--max-time 300`. The download now goes to a file (`$RUNNER_TEMP`) before being extracted by `tar`, rather than piping `curl` straight into `tar`, so that a retried transfer can safely restart without corrupting the tar stream. - **Attestation verification:** the `gh attestation verify` step, which also hits the network, is now wrapped in a retry loop (5 attempts with exponential backoff) before failing. ## Why A single transient network blip previously failed the whole job — for example [this rs-soroban-sdk run](https://github.com/stellar/rs-soroban-sdk/actions/runs/27120352954/job/80046147824) failed during the install step. With retries in place, a momentary failure is retried instead of failing the build. This mirrors the approach taken in [stellar/actions#104](stellar/actions#104), which added curl's built-in retry flags to harden a similar download path.

### What Bump the `crate-git-revision` build dependency in soroban-cli from 0.0.8 to 0.0.9, updating the workspace `Cargo.lock` to match. ### Why Keep the dependency current with its latest published release. ### Known limitations N/A --- _Generated by [Claude Code](https://claude.ai/code/session_013uNV6z846BVxfUtse4UA5X)_

### What Add an optional `--auth-mode` flag (and `STELLAR_AUTH_MODE` env var) to the commands that simulate Soroban transactions: `contract invoke`, `contract deploy`, `contract upload`, and `tx simulate`. Accept three modes: - `enforce` — validate the authorization entries already on the transaction. - `root` — record authorization entries, requiring each to be rooted at the transaction's top-level operation. - `non-root` — record all authorization entries, including non-root sub-invocation auth. Thread the selected mode into the RPC `simulateTransaction` `authMode` parameter through `simulate_and_assemble_transaction`. Leave the flag unset by default so `None` is passed and existing behavior is unchanged. Keep the flag off `extend`/`restore`, which do not produce `InvokeHostFunction` operations and which the RPC rejects an `authMode` for. ### Why Fixes #2574 The CLI is a developer-focused tool, but it previously had a single, fixed behavior for simulating Soroban authorization and could not produce, sign, or submit transactions that use non-root authorization. Exposing the RPC's auth modes lets developers opt into non-root authorization (and explicit enforce/record behavior) on the commands that build and simulate transactions. ### Known limitations - `enforce` auth mode is not valid on `invoke`/`deploy`/`upload`. It was kept to avoid having duplicate auth mode structs for simulation and invoke commands, and to match the RPC's interface. --------- Co-authored-by: Nando Vieira <[email protected]>

### What Updates protocol dependencies to protocol 27, cleans up clippy warnings, and adds the ability to sign AddressV2 auth entries. ### Known limitations Support for signing with delegated signers does not exist at this time

@mootz12

### What Bump version to 27.0.0, creating release branch. ### Why Triggered by @mootz12 in https://github.com/stellar/stellar-cli/actions/runs/27717910305. ### 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/v27.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/stellar-cli/releases/new?tag=v27.0.0&title=27.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/stellar-cli/releases/new?tag=v27.0.0&title=27.0.0&target=release/v27.0.0 Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

Navigation Menu

Uh oh!

Comparing changes

Open a pull request

Commits on May 28, 2026

Commits on May 29, 2026

Commits on Jun 1, 2026

Commits on Jun 2, 2026

Commits on Jun 3, 2026

Commits on Jun 4, 2026

Commits on Jun 5, 2026

Commits on Jun 8, 2026

Commits on Jun 16, 2026

Commits on Jun 17, 2026

This comparison is taking too long to generate.

Uh oh!