Update changelog (bd42de19) · Commits · Public Repositories / Smithy Rust

.changelog/1738340700.md

deleted100644 → 0

+0 −12

Original line number	Diff line number	Diff line
		---
		applies_to:
		- aws-sdk-rust
		authors:
		- ysaito1001
		references:
		- smithy-rs#3992
		breaking: false
		new_feature: false
		bug_fix: true
		---
		Stop populating `SessionMode` by default for the `CreateSession` API internally used by S3 Express. This will allow the service to choose a default value for `SessionMode` field based on bucket/access point being used.

.changelog/transfer-encoding-signing.md

deleted100644 → 0

+0 −10

Original line number	Diff line number	Diff line
		---
		applies_to: ["aws-sdk-rust"]
		authors: ["landonxjames"]
		references: ["smithy-rs#3991"]
		breaking: false
		new_feature: false
		bug_fix: true
		---

		Exclude `transfer-encoding` header from sigv4(a) signing since it is a hop by hop header that can be modified or removed by a proxy.

CHANGELOG.md

+3 −0

Original line number	Diff line number	Diff line
		<!-- Do not manually edit this file. Use the `changelogger` tool. -->
		February 3rd, 2025
		==================

		January 28th, 2025
		==================

aws/SDK_CHANGELOG.next.json

+33 −5

Original line number	Diff line number	Diff line
		@@ -17,7 +17,7 @@
		"aws-sdk-rust#1234"
		],
		"since-commit": "f7f037d3fda2d02b6a2ad1bce40dd84c787c6c35",
		"age": 4
		"age": 5
		},
		{
		"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",
		@@ -31,7 +31,7 @@
		"smithy-rs#3845"
		],
		"since-commit": "f7f037d3fda2d02b6a2ad1bce40dd84c787c6c35",
		"age": 4
		"age": 5
		},
		{
		"message": "Fix bug with presigned requests introduced by new flexibile checksums functionality\n",
		@@ -45,7 +45,7 @@
		"aws-sdk-rust#1240"
		],
		"since-commit": "733eab7e1a3678971ffa6bf9fb99826e17e99481",
		"age": 3
		"age": 4
		},
		{
		"message": "Allow IMDS clients to be configured with a user-provided `SharedRetryClassifier`.\n",
		@@ -59,7 +59,7 @@
		"aws-sdk-rust#1233"
		],
		"since-commit": "721e8a6762ed19194432bed0cb78b08a460d2fe4",
		"age": 2
		"age": 3
		},
		{
		"message": "Fix `EcsCredentialsProvider` to include query params passed via `AWS_CONTAINER_CREDENTIALS_RELATIVE_URI`.\n",
		@@ -73,7 +73,35 @@
		"aws-sdk-rust#1248"
		],
		"since-commit": "721e8a6762ed19194432bed0cb78b08a460d2fe4",
		"age": 2
		"age": 3
		},
		{
		"message": "Stop populating `SessionMode` by default for the `CreateSession` API internally used by S3 Express. This will allow the service to choose a default value for `SessionMode` field based on bucket/access point being used.\n",
		"meta": {
		"bug": true,
		"breaking": false,
		"tada": false
		},
		"author": "ysaito1001",
		"references": [
		"smithy-rs#3992"
		],
		"since-commit": "5ed776ffe2791f577639cb25c711002719809b3a",
		"age": 1
		},
		{
		"message": "Exclude `transfer-encoding` header from sigv4(a) signing since it is a hop by hop header that can be modified or removed by a proxy.\n",
		"meta": {
		"bug": true,
		"breaking": false,
		"tada": false
		},
		"author": "landonxjames",
		"references": [
		"smithy-rs#3991"
		],
		"since-commit": "5ed776ffe2791f577639cb25c711002719809b3a",
		"age": 1
		}
		],
		"aws-sdk-model": []

Admin message