migrate UPDATE_RELATIONSHIPV2 to UPDATE_RELATIONSHIP - 2.0.0 major re… #62
Conversation
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
…lease Why This is a Major Breaking Change API Signature Change: The method signature has fundamentally changed - from 1 required parameter to 3 required parameters Backward Incompatibility: Any existing code using update_relationship will break immediately GraphQL Mutation Change: The underlying GraphQL mutation has completely changed from updateRelationshipV2 to updateRelationship Response Structure Change: The response structure has also changed to include both relationship and edge objects
jayson-jensen-pro
approved these changes
Oct 14, 2025
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.
…lease
Why This is a Major Breaking Change
API Signature Change: The method signature has fundamentally changed - from 1 required parameter to 3 required parameters
Backward Incompatibility: Any existing code using update_relationship will break immediately
GraphQL Mutation Change: The underlying GraphQL mutation has completely changed from updateRelationshipV2 to updateRelationship
Response Structure Change: The response structure has also changed to include both relationship and edge objects