Protocol 28: bump go-stellar-sdk to protocol-next - #471
Draft
hunterpack wants to merge 1 commit into
Draft
Conversation
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
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
1 participant
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.
Part of the Protocol 28 epic (#470).
Bumps
go-stellar-sdkfrom v0.6.0 to v0.6.1-0.20260722220414-82df7643786e, the tip of the SDKprotocol-nextbranch, which includes the CAP-0085 XDR regeneration. Build and all unit tests pass. No transform changes are needed: nothing in stellar-etl switches onContractExecutableTypeor the newSCValarm, and SCVals are serialized generically through xdr-json.Still needed before merge:
go-stellar-xdr-jsononce its Protocol 28 release lands (blocked on stellar-xdr 28.0.0 on crates.io)Generated with Claude Code