Revert locked Rust dependencies to 517bea88fe93a259f28e02d13c6c0ef4a682b2d7#1044
Merged
Revert locked Rust dependencies to 517bea88fe93a259f28e02d13c6c0ef4a682b2d7#1044
Conversation
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
1 participant
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.
#1027 upgraded a bunch of dependencies, which somehow broke the AWS upload in the release pipeline.
This takes the
Cargo.lockfrom 517bea8 (the last successful release) then updates it (viacargo check) to match theCargo.tomlchanges from #1027. Consequently, some package versions are still upgraded, but not the full tree.This appears to have immediately resolved the AWS upload issue locally.