chore: adds transactional memory store#103
Merged
tanderson-ld merged 3 commits intomainfrom Jan 14, 2026
Merged
Conversation
tanderson-ld
commented
Jan 13, 2026
| "jackson": "2.11.2", | ||
| "launchdarklyJavaSdkCommon": "2.1.2", | ||
| "launchdarklyJavaSdkInternal": "1.5.1", | ||
| "launchdarklyJavaSdkInternal": "1.6.1", |
Contributor
Author
There was a problem hiding this comment.
For reviewers: I come from the future, and 1.6.1 solves all of humanities problems.
kinyoklion
approved these changes
Jan 14, 2026
Member
kinyoklion
left a comment
kinyoklion
left a comment
There was a problem hiding this comment.
Will need some gradle adjustments I think. The time machine went too far.
Contributor
Author
|
1.6.1 was correct, there was another fix released. |
tanderson-ld
deleted the
ta/SDK-1619/adding-transactional-memory-store
branch
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.
Requirements
Not possible yet
Related issues
SDK-1619
Describe the solution you've provided
Porting existing Dotnet SDK Impl