Skip to content

Bump soroban-env to next protocol version #595

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Shaptic merged 4 commits into from
Feb 19, 2026
Merged

Bump soroban-env to next protocol version #595

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
f9961de
Bump soroban-env to next protocol version
Shaptic Feb 3, 2026
86cc4b4
Add required config key to mocked ledger entries
Shaptic Feb 19, 2026
931e341
Prepare for P26 as curr
Shaptic Feb 19, 2026
350f37d
Integrate unstable-next-api into curr (dropped arg)
Shaptic Feb 19, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 1 addition & 3 deletions .github/workflows/stellar-rpc.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -90,14 +90,12 @@ jobs:
strategy:
matrix:
os: [ ubuntu-22.04 ]
protocol-version: [ 24, 25 ]
protocol-version: [ 25 ]
runs-on: ${{ matrix.os }}
env:
STELLAR_RPC_INTEGRATION_TESTS_ENABLED: true
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

@sisuresh sisuresh Feb 19, 2026

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?

@Shaptic Shaptic Feb 19, 2026

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? 🤔

PROTOCOL_25_CORE_DEBIAN_PKG_VERSION: 25.0.0-2911.e9748b05a.jammy
PROTOCOL_25_CORE_DOCKER_IMG: stellar/stellar-core:25.0.0-2911.e9748b05a.jammy

Expand Down
Loading
Loading