Skip to content

Add changelog entries for the next release - #138

Merged
jonathan343 merged 8 commits into
developfrom
changelog-codegen-sync-11-16
Nov 16, 2026
Merged

jonathan343 merged 8 commits into
developfrom
changelog-codegen-sync-11-16

Conversation

@jonathan343

@jonathan343 jonathan343 commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

Important

Merge this last, right before the next release. It follows the codegen sync in #140.

Summary

The next release needs changelog fragments for everything that changed since the 2026-10-08 release (v0.12.0). The new release infrastructure turns existing fragments into versions, changelogs, and tags. Apart from bump entries for the in-repo ~= pins it rewrites, it no longer writes initial-client, dependency, or meta-package entries, so this PR adds them under .changes/next-release/. Every service client has a feature or breaking entry, so all 37 release as 0.13.0.

The codegen sync entries cover smithy-python b8ecead...d185e3b, because the released clients were generated from b8ecead, not from the pointer's previous_commit. The API change entries copy the botocore 1.43.110 through 1.44.3 release notes for the 11 clients whose models changed, and each one was checked against the model diff. aws-credentials-http and aws-credentials-imds get the sync/aio entries removed in 3a7dd19, reworded.

aws-credentials-sts also gets fragments. 0.5.0 can't be installed, because it requires aws-sdk-sts~=0.12.0, which has no synchronous STSClient and pins an older smithy-aws-core. The in-repo pin has to match the sibling's current version, so the release step moves it to ~=0.13.0.

The release step rewrites in-repo pins in [project] dependencies and extras, but not in [dependency-groups]. So this PR also pins the aws-credentials-sts test group to the versions this release produces: aws-sdk-s3~=0.13.0, aws-credentials-http~=0.5.0, and aws-credentials-imds~=0.5.0. Without that, dep-specifiers fails after the release, because the test group's aws-sdk-s3~=0.12.0 disagrees with the meta package's ~=0.13.0.


By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@jonathan343
jonathan343 requested a review from a team as a code owner November 16, 2026 15:52
@jonathan343
jonathan343 force-pushed the changelog-codegen-sync-11-16 branch from 680c607 to 27ba302 Compare November 16, 2026 18:52
kuhe
kuhe previously approved these changes Nov 16, 2026
Clients were last released on 2026-10-08, generated with
smithy-python b8eceadb (codegen v0.6.0), so the entries cover
b8eceadb..ad7e0c04 rather than the pointer's previous_commit (481e133).

The 25 previously released clients get entries for synchronous clients
and the move of the async API to the aio modules, keyword operation
inputs, request dictionaries, endpoint rule resolution with FIPS and
dual-stack options, the adaptive retry mode, lazy models, py.typed and
model stubs, and Python 3.15. Per-service entries cover idempotency
tokens, DynamoDB account ID endpoints and retry defaults, SQS AWS Query
error codes, and ConnectHealth host prefixes.

aws-credentials-http and aws-credentials-imds get the sync/aio split
entries removed in 3a7dd19, reworded, plus a fix for the default
AIOHTTPClient never being closed and Python 3.15 support.

New clients, dependency bumps, and meta-package entries come from the
release infrastructure. API model entries follow separately.
…kage

The release infrastructure no longer writes initial-client, dependency, or
meta-package entries, so add them as next-release fragments with
new-entry.py. Every service client releases as 0.13.0.

- New clients: an initial release feature entry titled from the service
  model. They have no earlier release, so no dependency bumps.
- The 25 clients tagged v0.12.0: the smithy-core, smithy-aws-core, and
  smithy-http bumps.
- aws-sdk-python: support for the 12 new clients and a bump for each of
  the 37 service clients.
Copy the botocore 1.43.110 through 1.44.3 release notes for the 11
clients whose models changed since their v0.12.0 tags. Each entry was
checked against the model diff, and none repeats an entry already
released in 0.12.0.
aws-credentials-sts 0.5.0 requires aws-sdk-sts~=0.12.0, which has no
synchronous STSClient and pins an older smithy-aws-core, so it can't be
installed. Its in-repo pin must track the sibling's current version, so
the release step moves it to ~=0.13.0; these fragments make the package
part of that release.
GitHub's commits page doesn't accept a commit range, so the link showed no commits. The compare view lists the 97 commits from b8eceadb to ad7e0c04.
The release step adds a dependency entry for every in-repo ~= pin it rewrites, so the meta package's client bumps and aws-credentials-sts's aws-sdk-sts bump appeared twice in the 2026-11-16 release dry run.
The codegen pointer moves to smithy-python d185e3b5 in a separate PR, which
regenerates the clients against smithy-core 0.13.0, smithy-aws-core
0.16.0, and smithy-http 0.10.0 and picks up the @clientOptional fix.

End the codegen sync range at d185e3b5 and rename the codegen sync
fragments to match. Update the smithy dependency bumps for the 25
existing clients and aws-credentials-sts, and add the bumps that
aws-credentials-http and aws-credentials-imds were missing since 0.4.0.
The new codegen changes need no entries: the @clientOptional regression
never shipped, and S3 is a new client.
The release step rewrites in-repo pins in [project] dependencies and
extras, but not in [dependency-groups]. After the release, the test
group's aws-sdk-s3~=0.12.0 disagreed with the meta package's
aws-sdk-s3~=0.13.0, so dep-specifiers failed. Pin the test group to
the versions this release produces: aws-sdk-s3 0.13.0, and
aws-credentials-http and aws-credentials-imds 0.5.0.
@jonathan343
jonathan343 merged commit 7cb3c1a into develop Nov 16, 2026
5 checks passed
@jonathan343
jonathan343 deleted the changelog-codegen-sync-11-16 branch November 16, 2026 20:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants