From ae2882d247d2816b79422d115ca50a95e6a674c4 Mon Sep 17 00:00:00 2001
From: AWS SDK Rust Bot <aws-sdk-rust-primary@amazon.com>
Date: Wed, 19 Jun 2024 18:35:26 +0000
Subject: [PATCH] Update changelog

---
 CHANGELOG.md                | 13 +++++++++++++
 CHANGELOG.next.toml         | 15 +--------------
 aws/SDK_CHANGELOG.next.json | 12 ++++++------
 3 files changed, 20 insertions(+), 20 deletions(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index 940115473..386edd107 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,4 +1,17 @@
 <!-- Do not manually edit this file. Use the `changelogger` tool. -->
+June 19th, 2024
+===============
+**Breaking Changes:**
+- :bug::warning: (server, [smithy-rs#3690](https://github.com/smithy-lang/smithy-rs/issues/3690)) Fix request `Content-Type` header checking
+
+    Two bugs related to how servers were checking the `Content-Type` header in incoming requests have been fixed:
+
+    1. `Content-Type` header checking was incorrectly succeeding when no `Content-Type` header was present but one was expected.
+    2. When a shape was @httpPayload`-bound, `Content-Type` header checking occurred even when no payload was being sent. In this case it is not necessary to check the header, since there is no content.
+
+    This is a breaking change in that servers are now stricter at enforcing the expected `Content-Type` header is being sent by the client in general, and laxer when the shape is bound with `@httpPayload`.
+
+
 June 17th, 2024
 ===============
 
diff --git a/CHANGELOG.next.toml b/CHANGELOG.next.toml
index 662a6b6d2..fc4c4c257 100644
--- a/CHANGELOG.next.toml
+++ b/CHANGELOG.next.toml
@@ -9,17 +9,4 @@
 # message = "Fix typos in module documentation for generated crates"
 # references = ["smithy-rs#920"]
 # meta = { "breaking" = false, "tada" = false, "bug" = false, "target" = "client | server | all"}
-# author = "rcoh"
-[[smithy-rs]]
-message = """Fix request `Content-Type` header checking
-
-Two bugs related to how servers were checking the `Content-Type` header in incoming requests have been fixed:
-
-1. `Content-Type` header checking was incorrectly succeeding when no `Content-Type` header was present but one was expected.
-2. When a shape was @httpPayload`-bound, `Content-Type` header checking occurred even when no payload was being sent. In this case it is not necessary to check the header, since there is no content.
-
-This is a breaking change in that servers are now stricter at enforcing the expected `Content-Type` header is being sent by the client in general, and laxer when the shape is bound with `@httpPayload`.
-"""
-references = ["smithy-rs#3690"]
-meta = { "breaking" = true, "tada" = false, "bug" = true, "target" = "server"}
-author = "david-perez"
+# author = "rcoh"
\ No newline at end of file
diff --git a/aws/SDK_CHANGELOG.next.json b/aws/SDK_CHANGELOG.next.json
index f175ea5e5..3e376055e 100644
--- a/aws/SDK_CHANGELOG.next.json
+++ b/aws/SDK_CHANGELOG.next.json
@@ -18,7 +18,7 @@
         "smithy-rs#3673"
       ],
       "since-commit": "052b4dadc06354e673f6a642487871d5f50d135a",
-      "age": 3
+      "age": 4
     },
     {
       "message": "Fix S3 ListParts API paginator infinite loop.",
@@ -32,7 +32,7 @@
         "aws-sdk-rust#1143"
       ],
       "since-commit": "052b4dadc06354e673f6a642487871d5f50d135a",
-      "age": 3
+      "age": 4
     },
     {
       "message": "Stalled stream protection will no longer be applied to the following Lambda operations: [Invoke], [InvokeAsync], [InvokeWithResponseStream].\n\n[Invoke]: https://docs.rs/aws-sdk-lambda/latest/aws_sdk_lambda/client/struct.Client.html#method.invoke\n[InvokeAsync]: https://docs.rs/aws-sdk-lambda/latest/aws_sdk_lambda/client/struct.Client.html#method.invoke_async\n[InvokeWithResponseStream]: https://docs.rs/aws-sdk-lambda/latest/aws_sdk_lambda/client/struct.Client.html#method.invoke_with_response_stream\n",
@@ -47,7 +47,7 @@
         "smithy-rs#3639"
       ],
       "since-commit": "57ed310e6d21041eb36d825c50032295eef0b630",
-      "age": 1
+      "age": 2
     },
     {
       "message": "Add documentation on the default configuration to `from_env`, `load_from_env`, `defaults`, and `load_from_defaults` in the `aws-config` crate.",
@@ -61,7 +61,7 @@
         "aws-sdk-rust#1162"
       ],
       "since-commit": "57ed310e6d21041eb36d825c50032295eef0b630",
-      "age": 1
+      "age": 2
     },
     {
       "message": "Pre-signed requests may now be converted to Http v1.x requests. This requires enabling the `http-1x` feature for the SDK in question.\nThen, call `PresignedRequest::make_http_1x_request` or `PresignedRequest::into_http_1x_request`.\n",
@@ -75,7 +75,7 @@
         "smithy-rs#3696"
       ],
       "since-commit": "57ed310e6d21041eb36d825c50032295eef0b630",
-      "age": 1
+      "age": 2
     },
     {
       "message": "`AwsErrorCodeClassifier` for S3 now treats `InternalError` as a transient error to trigger retries.",
@@ -89,7 +89,7 @@
         "aws-sdk-rust#1163"
       ],
       "since-commit": "57ed310e6d21041eb36d825c50032295eef0b630",
-      "age": 1
+      "age": 2
     }
   ],
   "aws-sdk-model": []
-- 
GitLab