Update launchdarkly-server-sdk to version 2.5.1 #32036
Merged
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.
This updates the
launchdarkly-server-sdk
dependency to version 2.5.1.We are still using our own fork mostly because it has MaterializeInc/rust-server-sdk@4d051dd which we can't easily upstream because it doesn't fully solve the issue (see Slack thread). We may be able to depend on upstream again once launchdarkly/rust-server-sdk#116 is resolved. We are able to move back to upstream for the
rust-eventsource-client
crate at least.Motivation
Closes https://github.com/MaterializeInc/database-issues/issues/9113
Tips for reviewer
I rebased our
rust-server-sdk
fork by pushing to main directly, so there is no PR to review. However, you can view the changes relative to the upstream here. Also the old state of main is still available as the main-backup branch.Checklist
$T ⇔ Proto$T
mapping (possibly in a backwards-incompatible way), then it is tagged with aT-proto
label.