Skip to content

Bump soroban-env to next protocol version - #595

Merged
Shaptic merged 4 commits into
protocol-nextfrom
bump-env
Feb 19, 2026
Merged

Shaptic merged 4 commits into
protocol-nextfrom
bump-env

Conversation

@Shaptic

@Shaptic Shaptic commented Feb 3, 2026

Copy link
Copy Markdown
Contributor

What

Bumps soroban-env major versions.

Why

Prepare RPC for P26 iterative testing.

Known limitations

n/a

@Shaptic
Shaptic changed the base branch from protocol-26 to protocol-next February 3, 2026 23:53
STELLAR_RPC_INTEGRATION_TESTS_CORE_MAX_SUPPORTED_PROTOCOL: ${{ matrix.protocol-version }}
STELLAR_RPC_INTEGRATION_TESTS_CAPTIVE_CORE_BIN: /usr/bin/stellar-core
PROTOCOL_24_CORE_DEBIAN_PKG_VERSION: 25.0.0-2911.e9748b05a.jammy
PROTOCOL_24_CORE_DOCKER_IMG: stellar/stellar-core:25.0.0-2911.e9748b05a.jammy

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This can be done in a follow up if that makes more sense, but we have a vnext core image available in the internal registry - 25.1.2-3029.781d3b1d2.jammy~vnext. Can this pull from the internal registry or do the images need to exist in Dockerhub?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The GHA doesn't have access to the internal registry, no. But we can combine this with #606 to build from source? 🤔

@Shaptic
Shaptic requested a review from a team February 19, 2026 22:56
@Shaptic
Shaptic merged commit 83953e4 into protocol-next Feb 19, 2026
36 of 38 checks passed
@Shaptic
Shaptic deleted the bump-env branch February 19, 2026 23:29
Comment thread Cargo.lock
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "98d1ed4701671ad02eb719062bf61f83a71cd8da3566c21e71f4065120cdeb6c"
version = "26.0.0-rc.1"
source = "git+https://github.com/stellar/rs-soroban-env.git#aab7c15d2b3ba441a1a6fd741719ecf6f6729f66"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Shaptic This commit of env is out of date. Should we explicitly set the branch in the toml file to main?

Shaptic added a commit that referenced this pull request Mar 5, 2026
* Bump soroban-env to next protocol version
* Add required config key to mocked ledger entries
* Integrate unstable-next-api into curr (dropped arg)
Shaptic added a commit that referenced this pull request Mar 10, 2026
* Bump soroban-env to next protocol version
* Add required config key to mocked ledger entries
* Integrate unstable-next-api into curr (dropped arg)
Shaptic added a commit that referenced this pull request Mar 10, 2026
* Bump soroban-env to next protocol version
* Add required config key to mocked ledger entries
* Integrate unstable-next-api into curr (dropped arg)
Shaptic added a commit that referenced this pull request Mar 17, 2026
* Bump soroban-env to next protocol version
* Add required config key to mocked ledger entries
* Integrate unstable-next-api into curr (dropped arg)
Shaptic added a commit that referenced this pull request Mar 31, 2026
* Bump soroban-env to next protocol version (#595)
 - Add required config key to mocked ledger entries
 - Integrate unstable-next-api into curr (dropped arg)

* Update XDR and Core runs to test P26 integration (#629)
 - Bump Golang to 1.25 and linter to be compatible
 - Bumped Go SDK to latest @protocol-next
 - Added P26 limits from quickstart and removed P24 limits

* Fix deluge of linter complaints on branch merge (#646)

---------

Co-authored-by: Siddharth Suresh <siddharth@stellar.org>
karthikiyer56 added a commit that referenced this pull request Apr 9, 2026
* Bump soroban-env to next protocol version (#595)

* Bump soroban-env to next protocol version
* Add required config key to mocked ledger entries
* Integrate unstable-next-api into curr (dropped arg)

* Bump soroban-env SHA to latest (#611)

* Update XDR and Core runs to test P26 integration (#629)

* Split the single core_version input into core_deb_version and core_docker_img to accommodate differences.
* Bump Core versions for P25 and add P26 run
* Bump Golang to 1.25 and linter to be compatible
* Bumped soroban-env-host curr to latest commit SHA in repo
* Bumped Go SDK to latest @protocol-next
* Added P26 limits from quickstart and removed P24 limits

* Bump crate dependencies to latest Protocol 26 versions (#640)

* Remove unimplemented GitHub Action (#643)

Snuck in with a `git add -A` on accident

* Bump Core to Protocol 26 release candidate (#642)

* Bump Core to p26 release candidate
* Bump Go SDK version to latest
* Bump to official patched env

* Ensure we strip NUL bytes before `CString::new` (#632)

* Fix deluge of linter complaints on branch merge (#646)

* Release v26.0.0 (#647)

* Tag off changelog for major release
* Bump Go SDK to official P26 version
* Bump CI to latest stable core for a final run

* Add GHA to automatically update soroban-env on protocol-next (#645)

* Preserve version string in Cargo.toml on automatic dependency bump (#672)

* Preserve version= in Cargo.toml on bump
* Simplify code: use a function, better names

* Bump to soroban-env to latest version (#673)

---------

Co-authored-by: George <Shaptic@users.noreply.github.com>
Co-authored-by: Siddharth Suresh <siddharth@stellar.org>
Co-authored-by: George <george@stellar.org>
sisuresh added a commit to sisuresh/stellar-rpc that referenced this pull request May 28, 2026
Shift the preflight multi-protocol window to p27 using the pre-release
git-ref pattern (cf. stellar#595): advance -prev to the released p26
soroban-env-host/soroban-simulation 26.0.1, and point -curr at
rs-soroban-env @7fb0a840 (the p27/CAP-71 host core uses) + rs-stellar-xdr
@a749b69b with the cap_0071 feature. Adapt xdr2json to that stellar-xdr's
single-module layout and the prev load_from_snapshot 1-arg signature.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants