Remove version constraint for smithy-core in intermediate packages #616
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.
Summary
#562 added minor version constraints on
smithy-coreusing~=in intermediate packages such assmithy-httpandsmithy-json. This provided more strict compatibility, however, it also means that we have many unnecessary package bumps in the case where smithy-core receives a minor version bump.This PR reverts the smithy-core constraint and we will rely on the constraints defined in smithy-aws-core and all AWS client packages. This prevents us from have to do unnecessary minor version bumps for intermediate packages in the future.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.