Updated CHANGELOG for release v1.7.1 #377
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -7,6 +7,17 @@ Unreleased | |
| ### SDK Bugs | ||
|
|
||
|
|
||
| Release v1.7.1 (2022-09-14) | ||
| ================================ | ||
| ### SDK Enhancements | ||
|
|
||
| ### SDK Bugs | ||
| * Replace error type assertions with errors.As in DefaultFormattingStrategy [#PR 353](https://github.com/aws/aws-xray-sdk-go/pull/353) | ||
| * Dummy segments don't need cancel go routine [#PR 365](https://github.com/aws/aws-xray-sdk-go/pull/365) | ||
|
There was a problem hiding this comment. For each change, if it would be considered a PATCH change by the definitions of https://semver.org/, it should be considered a bug fix. For example, I think this would probably be considered a backwards-compatible bug fix rather than adding functionality |
||
| * Strip X-Amz-Security-Token from SQL URIs [#PR 367](https://github.com/aws/aws-xray-sdk-go/pull/367) | ||
| * Upgrading Go Version [#PR 379](https://github.com/aws/aws-xray-sdk-go/pull/379) | ||
|
|
||
|
|
||
| Release v1.7.0 (2022-04-11) | ||
| ================================ | ||
| ### SDK Enhancements | ||
|
|
@@ -212,7 +223,7 @@ Release v1.0.0-rc.7 (2018-09-27) | |
| Release v1.0.0-rc.6 (2018-09-25) | ||
| ================================ | ||
| ### SDK Breaking changes | ||
| * The default sampling strategy is `CentralizedStrategy` that launches background tasks to poll sampling rules from X-Ray backend. See the new default sampling strategy in more details | ||
| here: [Link](https://docs.aws.amazon.com/xray/latest/devguide/xray-sdk-go-configuration.html#xray-sdk-go-configuration-sampling) | ||
| * The `ShouldTrace()` function in the `Strategy` interface now takes a `Request` structure for sampling rule matching and returns `Decision` object | ||
| * Updated `aws-sdk-go` version in `glide.yaml` file to `1.15.23`. | ||
|
|
@@ -266,12 +277,11 @@ Release v1.0.0-rc.1 (2018-01-15) | |
| * Remove attempt number when AWS SDK retries. | ||
| * Make HTTP requests if segment doesn't exist. | ||
| * Add Go SDK Version, Go Compiler and X-Ray SDK information in segment document. | ||
| * Set remote value when AWS request fails due to a service-side error. | ||
|
|
||
| Release v0.9.4 (2017-09-08) | ||
| =========================== | ||
| ### SDK Enhancements | ||
| * Refactor code to fit Go Coding Standard. | ||
| * Update README. | ||
| * `aws-xray-sdk-go/xray`: make HTTP request if segment cannot be found. | ||
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry I should have been more clear - basically what we want to do is go through each change, and decide if it's an "enhancement" or a "bug fix" based on the semver definition, and put it under the appropriate header.
Then, if there are any "enhancements" in this release, it should be a MINOR version (1.8.0). If it's all bug fixes, it's just a patch (1.7.1). Please let me know if you have any questions!