chore: Bump keyring to 3.6.1 #305
Merged
Conversation
This file contains 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
joonas
force-pushed
the
chore/update-keyring
branch
2 times, most recently
from
65d6836 to
50ffa90
Compare
Signed-off-by: Joonas Bergius <[email protected]>
joonas
force-pushed
the
chore/update-keyring
branch
from
50ffa90 to
27e293c
Compare
calvinrp
approved these changes
Nov 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This updates
keyringdependency to the latest available version to address outstanding RUSTSEC advisories.As part of the bump, I also adapted
FlatfileCredentialbackend to implement the newly introducedCredentialApimethods.Please note that I've selected
async-secret-servicewithasync-iobackend to maintain compatibility with the previous defaults.