Skip to content

Conversation

@SamRemis
Copy link
Contributor

Prepare release of standard retry mode and add minor version bumps for it

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

Copy link
Contributor

@jonathan343 jonathan343 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks Sam! Left a few comments. You're missing a few steps for each package in this PR:

  • We need to run ./scripts/new-release -p <package_name> -v <package_version>
  • Then run ./scripts/render -p <package_name> -o packages/<package_name>/CHANGELOG.md
  • Was not including the bumps in SmithyPythonDependency.java intentional? We need that to have new SDKs get generated with the new minor versions


__license__ = "Apache-2.0"
__version__ = "0.1.0"
__version__ = "0.2.0"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why does signers need a minor version bump? This is a leaf note in the dependency tree of the SDKs and smithy-aws-core. There are also no new changes being added to this package. Personally, I don't think we should be bumping this.

from .interfaces import FieldPosition

__version__ = "0.2.1"
__version__ = "0.3.0"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I feel like we may also want to have a changelong entry for #590. Not sure if that was a miss in the original PR or intentional.

@@ -0,0 +1,4 @@
{
"type": "dependency",
"description": "Bump dependencies on smithy-core, smithy-http, and aws-sdk-signers for minor release"
Copy link
Contributor

@jonathan343 jonathan343 Nov 21, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. This is missing bumps for smithy-aws-event-stream and smithy-json.
  2. Definitely debatable, but personally, I think each should have their own entry using the format I provided in a different comment. They would eventually get rendered in the changelog as:

Dependencies

  • Bump smithy-core from ~=0.1.0 to ~=0.2.0.
  • Bump smithy-http from ~=0.2.0 to ~=0.3.0.
  • Bump smithy-aws-event-stream from ~=0.1.0 to ~=0.2.0.
  • Bump smithy-json from ~=0.1.0 to ~=0.2.0.

SamRemis and others added 3 commits November 21, 2025 11:18
…aws-event-stream-dependency-20251121101319.json

Co-authored-by: jonathan343 <43360731+jonathan343@users.noreply.github.com>
@SamRemis SamRemis marked this pull request as ready for review November 21, 2025 17:02
@SamRemis SamRemis requested a review from a team as a code owner November 21, 2025 17:02
Copy link
Contributor

@jonathan343 jonathan343 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! 🚢

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