prepare 7.0.0 release #208
Merged
Conversation
This file contains 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
…rting stream in this case
…-warning (#1) make logging of big segments patch version mismatch clearer and use Warn level
(#2) fix DynamoDB updates for big segments metadata
# Conflicts: # internal/core/bigsegments/sync.go
(#3) only start big seg synchronizer if necessary
# Conflicts: # go.mod # go.sum
fix retry logic on big segments stream failure
…gging add more logging for big segments connection status
more big segments integration tests + fix flaky unit tests
move Relay release logic to .ldrelease script
bump minimum Go to 1.18, build images in 1.19, update SDK
* remove obsolete "eval" endpoints superseded by "evalx" * fix tests & examples * fix more tests
update to Go 1.19.2
# Conflicts: # .circleci/config.yml # .golangci.yml # Makefile # go.mod # go.sum # internal/bigsegments/store.go # internal/bigsegments/store_dynamodb.go # internal/bigsegments/store_dynamodb_test.go # internal/core/relay_core.go # internal/core/relay_core_endpoints_status.go # internal/core/relay_core_endpoints_test.go # internal/filedata/archive_reader.go # internal/sdks/data_stores.go # internal/sdks/data_stores_test.go # relay/relay_endpoints.go
use latest Go SDK prerelease packages, update for API changes
streamline test code using go-test-helpers v3
cwaldren-ld
approved these changes
Dec 7, 2022
louis-launchdarkly
approved these changes
Dec 7, 2022
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
[7.0.0] - 2022-12-07
The latest version of the Relay Proxy supports LaunchDarkly's new custom contexts feature. Contexts are an evolution of a previously-existing concept, "users." Contexts let you create targeting rules for feature flags based on a variety of different information, including attributes pertaining to users, organizations, devices, and more. You can even combine contexts to create "multi-contexts."
This feature is only available to members of LaunchDarkly's Early Access Program (EAP). If you're in the EAP, and the SDK you are using also has an EAP release, you can use contexts by updating your SDK to the latest version and, updating your Relay Proxy. Outdated SDK versions do not support contexts, and will cause unpredictable flag evaluation behavior.
If you are not in the EAP, only use single contexts of kind "user", or continue to use the user type if available. If you try to create contexts, the context will be sent to LaunchDarkly, but any data not related to the user object will be ignored.
For detailed information about this version, please refer to the list below.
Added:
Changed:
Removed: