diff --git a/CHANGELOG.md b/CHANGELOG.md
index 74853500..7c018ae7 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,3 +1,12 @@
+Release v1.4.0 (2021-05-03)
+================================
+### SDK Enhancements
+* No op trace id generation support for unsampled traces [PR #293](https://github.com/aws/aws-xray-sdk-go/pull/293)
+* Refactored `httpTrace` method [PR #296](https://github.com/aws/aws-xray-sdk-go/pull/296)
+
+### SDK Bugs
+* Fix panic issue when call `AddError` function [PR #288](https://github.com/aws/aws-xray-sdk-go/pull/288)
+
 Release v1.3.0 (2021-02-02)
 ================================
 ### SDK Enhancements
diff --git a/README.md b/README.md
index bd4b7091..26aba121 100644
--- a/README.md
+++ b/README.md
@@ -152,6 +152,10 @@ Note that customers using xray.BeginSegment API directly will only be able to ev
   seg.Close(nil)
 ```
 
+**Generate no-op trace and segment id**
+
+X-Ray Go SDK will by default generate no-op trace and segment id for unsampled requests and secure random trace and entity id for sampled requests. If customer wants to enable generating secure random trace and entity id for all the (sampled/unsampled) requests (this is applicable for trace id injection into logs use case) then they achieve that by setting AWS_XRAY_NOOP_ID environment variable as False.
+
 **Disabling XRay Tracing**
 
 XRay tracing can be disabled by setting up environment variable `AWS_XRAY_SDK_DISABLED` . Disabling XRay can be useful for specific use case like if customer wants to stop tracing in their test environment they can do so just by setting up the environment variable.
diff --git a/xray/config.go b/xray/config.go
index 842befb0..9d45b723 100644
--- a/xray/config.go
+++ b/xray/config.go
@@ -24,7 +24,7 @@ import (
 )
 
 // SDKVersion records the current X-Ray Go SDK version.
-const SDKVersion = "1.3.0"
+const SDKVersion = "1.4.0"
 
 // SDKType records which X-Ray SDK customer uses.
 const SDKType = "X-Ray for Go"