diff --git a/.changelog/1736370747.md b/.changelog/1736370747.md
deleted file mode 100644
index 65c2c209b76590835509e61d6f5503be648100e1..0000000000000000000000000000000000000000
--- a/.changelog/1736370747.md
+++ /dev/null
@@ -1,13 +0,0 @@
----
-applies_to:
-- aws-sdk-rust
-- client
-authors:
-- aajtodd
-references:
-- aws-sdk-rust#1234
-breaking: false
-new_feature: false
-bug_fix: true
----
-Fix token bucket not being set for standard and adaptive retry modes
diff --git a/.changelog/flexible-checksums-client.md b/.changelog/flexible-checksums-client.md
deleted file mode 100644
index ee69e3fd408b0a2b47d6f97bb00876bedb2edc6d..0000000000000000000000000000000000000000
--- a/.changelog/flexible-checksums-client.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-applies_to: ["client"]
-authors: ["landonxjames"]
-references: ["smithy-rs#3967"]
-breaking: false
-new_feature: true
-bug_fix: true
----
-
-Updates client generation to conform with Smithy's updates to the [httpChecksum trait](https://smithy.io/2.0/aws/aws-core.html#aws-protocols-httpchecksum-trait).
diff --git a/.changelog/flexible-checksums-s3.md b/.changelog/flexible-checksums-s3.md
deleted file mode 100644
index 0e903e9a2adbdcbed129d2da172f00fbd7c4e1d2..0000000000000000000000000000000000000000
--- a/.changelog/flexible-checksums-s3.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-applies_to: ["client", "aws-sdk-rust"]
-authors: ["landonxjames"]
-references: ["smithy-rs#3845"]
-breaking: false
-new_feature: true
-bug_fix: true
----
-
-S3 client behavior is updated to always calculate a checksum by default for operations that support it (such as PutObject or UploadPart), or require it (such as DeleteObjects). The default checksum algorithm is CRC32. Checksum behavior can be configured using `when_supported` and `when_required` options - in shared config using request_checksum_calculation, or as env variable using AWS_REQUEST_CHECKSUM_CALCULATION.
-
-The S3 client attempts to validate response checksums for all S3 API operations that support checksums. However, if the SDK has not implemented the specified checksum algorithm then this validation is skipped. Checksum validation behavior can be configured using `when_supported` and `when_required` options - in shared config using response_checksum_validation, or as env variable using AWS_RESPONSE_CHECKSUM_VALIDATION.
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 08c286768cd9be8f21f5f5fcaad0cf19e4075ae5..0ac468fc4befcc327251e000afc57bea8cdda7a7 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,4 +1,14 @@
 <!-- Do not manually edit this file. Use the `changelogger` tool. -->
+January 14th, 2025
+==================
+**New this release:**
+- :bug::tada: (client, [smithy-rs#3845](https://github.com/smithy-lang/smithy-rs/issues/3845)) S3 client behavior is updated to always calculate a checksum by default for operations that support it (such as PutObject or UploadPart), or require it (such as DeleteObjects). The default checksum algorithm is CRC32. Checksum behavior can be configured using `when_supported` and `when_required` options - in shared config using request_checksum_calculation, or as env variable using AWS_REQUEST_CHECKSUM_CALCULATION.
+
+    The S3 client attempts to validate response checksums for all S3 API operations that support checksums. However, if the SDK has not implemented the specified checksum algorithm then this validation is skipped. Checksum validation behavior can be configured using `when_supported` and `when_required` options - in shared config using response_checksum_validation, or as env variable using AWS_RESPONSE_CHECKSUM_VALIDATION.
+- :bug::tada: (client, [smithy-rs#3967](https://github.com/smithy-lang/smithy-rs/issues/3967)) Updates client generation to conform with Smithy's updates to the [httpChecksum trait](https://smithy.io/2.0/aws/aws-core.html#aws-protocols-httpchecksum-trait).
+- :bug: (client, [aws-sdk-rust#1234](https://github.com/awslabs/aws-sdk-rust/issues/1234)) Fix token bucket not being set for standard and adaptive retry modes
+
+
 December 30th, 2024
 ===================
 
diff --git a/aws/SDK_CHANGELOG.next.json b/aws/SDK_CHANGELOG.next.json
index 013f5c15f10ec456895c4e9b0cab6bde06305e48..97aa12586e158fe41ccdc5747037cec7ed613ba3 100644
--- a/aws/SDK_CHANGELOG.next.json
+++ b/aws/SDK_CHANGELOG.next.json
@@ -15,7 +15,7 @@
       "author": "Velfi",
       "references": [],
       "since-commit": "039177d0ee6dd288ad57de2230a1110bbe7ff7d5",
-      "age": 4
+      "age": 5
     },
     {
       "message": "It is now possible to disable payload signing through an operation customization.\n\n```rust\nasync fn put_example_object(client: &aws_sdk_s3::Client) {\n    let res = client\n        .put_object()\n        .bucket(\"test-bucket\")\n        .key(\"test-key\")\n        .body(ByteStream::from_static(b\"Hello, world!\"))\n        .customize()\n        // Setting this will disable payload signing.\n        .disable_payload_signing()\n        .send()\n        .await;\n}\n```\n\nDisabling payload signing will result in a small speedup at the cost of removing a data integrity check.\nHowever, this is an advanced feature and **may not be supported by all services/operations**.\n",
@@ -29,7 +29,35 @@
         "smithy-rs#3583"
       ],
       "since-commit": "89881abd3df80e9b6fd59790d7c02e2b9a6dd45c",
-      "age": 3
+      "age": 4
+    },
+    {
+      "message": "Fix token bucket not being set for standard and adaptive retry modes\n",
+      "meta": {
+        "bug": true,
+        "breaking": false,
+        "tada": false
+      },
+      "author": "aajtodd",
+      "references": [
+        "aws-sdk-rust#1234"
+      ],
+      "since-commit": "f7f037d3fda2d02b6a2ad1bce40dd84c787c6c35",
+      "age": 1
+    },
+    {
+      "message": "S3 client behavior is updated to always calculate a checksum by default for operations that support it (such as PutObject or UploadPart), or require it (such as DeleteObjects). The default checksum algorithm is CRC32. Checksum behavior can be configured using `when_supported` and `when_required` options - in shared config using request_checksum_calculation, or as env variable using AWS_REQUEST_CHECKSUM_CALCULATION.\n\nThe S3 client attempts to validate response checksums for all S3 API operations that support checksums. However, if the SDK has not implemented the specified checksum algorithm then this validation is skipped. Checksum validation behavior can be configured using `when_supported` and `when_required` options - in shared config using response_checksum_validation, or as env variable using AWS_RESPONSE_CHECKSUM_VALIDATION.\n",
+      "meta": {
+        "bug": true,
+        "breaking": false,
+        "tada": true
+      },
+      "author": "landonxjames",
+      "references": [
+        "smithy-rs#3845"
+      ],
+      "since-commit": "f7f037d3fda2d02b6a2ad1bce40dd84c787c6c35",
+      "age": 1
     }
   ],
   "aws-sdk-model": []