Update SurrealDB SDKs to latest 2.x (2.6.5) and 3.x (3.1.5) - #94
Merged
Conversation
Bump both SDK lines to their latest stable releases while keeping v2/v3 coexistence, align test/loadtest Docker image tags, and configure Dependabot to ignore cross-major surrealdb upgrades.
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.
What is the motivation?
surreal-sync supports SurrealDB 2.x and 3.x at the same time, so both SDK lines should track their own latest stable release. Dependabot instead tried to collapse 2.x onto 3.x (#88), which breaks that dual-SDK support.
What does this change do?
surrealdbupgrades.What is your testing strategy?
make clippyandmake test(unit, integration against live 2.6.5/3.1.5 containers, and doctests) pass locally.Is this related to any issues?
#88
Have you read the Contributing Guidelines?