Repository navigation
Conversation
Contributor
Author
|
Closing at the maintainers' request: the next release will be 1.8.0, and the Smithy team will handle the version bump. Feel free to reuse the CHANGELOG draft and the reviewer notes in this PR's description. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What behavior changes?
Bumps
VERSIONfrom1.7.0to1.7.1and adds the 1.7.1 entry toCHANGELOG.md. There are no code changes.The release covers 52 commits since 1.7.0 (
1.7.0..d62ebebbe, 35 PRs). The main reason for it is three MCP fixes:Why is this change needed?
Consumers of the MCP server need these fixes released. Clients are moving their default to MCP protocol 2026-07-28, and on 1.7.0, tool calls to remotes that validate the
MCP-Protocol-Versionheader fail. Remotes that answer a notification with a202and a body also fail to initialize.How was this validated?
Release preflight from the internal release process, run on
d62ebebbewithVERSION=1.7.1:./gradlew clean build publishpassed, with:client:client-waiters:testskipped becauseTestWaiters.testWaiterTimesOutis flaky (see below).bomskipped as usual). No new modules need onboarding.ba1901282passed. Build links are in the internal tracking ticket.This commit sits directly on
d62ebebbe, so the merged tree is exactly what was dry-run plusVERSIONandCHANGELOG.md.What should reviewers focus on?
The CHANGELOG entry is a best-effort draft. Please correct anything that's wrong.
## 1.7.1 (TBD). Set the date before merging. 1.7.0 used theM/D/YYYYformat.IllegalStateException, andclose()on a pooled body does nothing. A customClientTransportthat keeps reading the body after it returns must callPooledDataStream.abandon(). Each built-in protocol now owns its own pool, which can keep up to about 4 MB of arrays per size class.Signer/IdentityResolverand can be shared across calls. Implementations that mutated them may break.StructDocumentnumber coercion uses narrowing casts, so out-of-range or fractional values are truncated silently.EventStreamSchemaExtensionsservice provider. Shaded JARs that dropMETA-INF/serviceswill fail.aws.userAgentAppIdis now honored, and the app ID is resolved once per client build.server-nettyusers.TestWaiters.testWaiterTimesOut: failed 2 of 3 isolated reruns.Waiter.waitToRetrychecksremainingTime < 0. At exactly 0 it retries with no delay and the mock runs out of responses, so the check should probably be<= 0.RestJson1ProtocolTests›UnmodeledProtocolErrorinaws-client-restjson:integ-native: failed once under a parallel full build and passed when rerun alone.Bump version to 1.7.1.update_release_tagsfinds the release commit by that subject.Commit → PR mapping (52 commits)
d62ebebbe8e892b96c4a8bea126StructDocumentnumbers)70c0f918e4bb3eaad39341050c4ac39c17af8820b722cb386e9aca7aa78c1682ac9166c1be145fcabb11fd4417ec12fbba2f12e11a6baws.partition, plus benchmark)51bc74f0467e1f063c473877a37ba1901282d3dd17843304e025110e88c8e76c62499ffde839b1b49156e5939d2fd0f976f2e6f15e600f0bedf59ebe122c961f68318ce534de7824500cc0d5c298b5d799d5bbff7be83331aaf1057770a2c8f038fd5a8c5cf2907eb23fa19f142eecf4d852d8ab7a9326586abcb0406f987280900694e51ae1edoneOf, timestamps)9a262167c225ebe17b27ff34d36f7216c2062c9b5e49cSchemasmethod size limit)5d0812981d70d5a564protocol-test-harness)Additional Links
subscriptions/listen, not included)By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
🤖 AI-assisted PR description 🤖