From 91c7ba4cfde7cf301ac844c58b198496289dd45a Mon Sep 17 00:00:00 2001 From: LaunchDarklyCI Date: Fri, 26 Apr 2019 00:12:29 +0000 Subject: [PATCH] Update Changelog for release of version 4.7.2 --- CHANGELOG.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index dda3b49..adce477 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -2,6 +2,21 @@ All notable changes to the LaunchDarkly Go SDK will be documented in this file. This project adheres to [Semantic Versioning](http://semver.org). +## [4.7.2] - 2019-04-25 +### Changed: +- The default value for the `Config` property `Capacity` (maximum number of events that can be stored at once) is now 10000, consistent with the other SDKs, rather than 1000. + +### Fixed: +- If `Track` or `Identify` is called without a user, the SDK now will not send an analytics event to LaunchDarkly (since it would not be processed without a user). +- The size of the SDK codebase has been reduced considerably by eliminating unnecessary files from `vendor`. + +## Note on future releases +The LaunchDarkly SDK repositories are being renamed for consistency. All future releases of the Go SDK will use the name `go-server-sdk` rather than `go-client`. The import path will change to: + + "gopkg.in/launchdarkly/go-server-sdk.v4" + +Since Go uses the repository name as part of the import path, to avoid breaking existing code, we will retain the existing `go-client` repository as well. However, it will not be updated after this release. + ## [4.7.1] - 2019-01-09 ### Fixed: - Fixed a potential race condition in the DynamoDB and Consul feature store integrations where it might be possible to see a feature flag that depended on a prerequisite flag (or on a user segment) before the latter had been written to the store.