Point future image at futurenet's protocol 28 builds - #962
Merged
Conversation
The future image pinned protocol 26 releases while futurenet has moved to protocol 28 vnext builds, so it could not join futurenet and its rpc v26 pin no longer compiles on stable Rust. Pin core, rpc, and horizon to the commits futurenet reports running, and xdr to the commit that ungates CAP-0083/CAP-0085 (no release has it yet). Move galexie to its latest release and lab to main, matching the other images -- neither has protocol 28 support to track. Bump nightly-next's default protocol to 28 to match futurenet. Fixes stellar#960
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the future image for Futurenet protocol 28 and resolves the obsolete RPC v26 build failure.
Changes:
- Pins protocol-28-compatible Core, RPC, Horizon, and XDR commits.
- Updates Laboratory and Galexie references.
- Sets future-facing images to protocol 28.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
leighmcculloch
approved these changes
Jul 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
futureimage still pinned protocol 26 releases, so it can't join futurenet (now on protocol 28) and its rpc v26 pin no longer compiles on stable Rust. This pins core, rpc, and horizon to the commits futurenet reports running, and xdr to the CAP-0083/CAP-0085 ungate commit since no release has it yet.galexie moves to its latest release and lab to
main— neither has protocol 28 support to track.nightly-next's default protocol goes to 28 to match futurenet.Fixes #960, unblocks #961.