Conversation
This keeps v3 consumers on the last compatible release while preparing the latest SDK changes for a proper v4.0.0 release. Made-with: Cursor
Document the breaking balance API changes and the migration steps for schema and SDK consumers. Made-with: Cursor
Preserve the v3.1.0 upgrade note and describe the new breaking changes as the v4.0.0 upgrade from v3.1.0. Made-with: Cursor
sophiehouser
approved these changes
Mar 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
2 participants
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.
Summary
github.com/fragment-dev/fragment-go/v3togithub.com/fragment-dev/fragment-go/v4/v4v3.0.0as the last pre-breaking v3 release while preparing the latest SDK changes forv4.0.0Test plan
go test ./...go get github.com/fragment-dev/fragment-go/v4@v4.0.0after taggingv3.0.0already points to the pre-breaking commit/v4v4.0.0tag after the PR is mergedMade with Cursor