Synchronize the SDK lockfile during release #3838
Merged
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.
Description
This PR introduces an additional step to the
generate-smithy-rs-release
script to synchronize the SDK lockfile with the runtime lockfiles and the Cargo dependencies specified in CargoDependency.kt. For more details on why we synchronize the SDK lockfile, please refer to the sdk-lockfiles README.We've decided to synchronize the SDK lockfile during release for the following reasons:
Testing
Tested with the following scenario:
aws-smithy-runtime
and updatedrust-runtime/Cargo.lock
sdk-lockfiles audit
failed as expectedaws-smithy-runtime
crate version and adding dummy dependencies.sdk-lockfiles audit
succeeded in the release artifactsBy submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.