-
Notifications
You must be signed in to change notification settings - Fork 18.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump notary version to 0.4.2 #27074
Bump notary version to 0.4.2 #27074
Conversation
ping @riyazdf @endophage |
SGTM |
LGTM! |
^sorry, fixed an error message typo in two of the tests |
LGTM |
1 similar comment
LGTM |
bump. :) can this be merged? |
Looks like some related commits could be squashed, or are we good with having them all separate? |
@thaJeztah I have no strong feelings. I can squash them if you like. |
Signed-off-by: cyli <cyli@twistedmatrix.com>
- some function signatures have changed - use the new ones - re-generate the notary delegation key certs, since notary doesn't allow SHA1 - fix some error message mapping because now if a root rotation fails to validate trusted operations will fail Signed-off-by: cyli <cyli@twistedmatrix.com>
@cyli perhaps split in "bump" commits and "fix" commits |
oh! done already, haha |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Bump notary version to 0.4.2
This bumps the notary dependency up to 0.4.2 (full changelogs here).
The docker-client-relevant behavior changes are:
~/.docker/trust/private
directory, not just under~/.docker/trust/private/root_keys
or ``~/.docker/trust/private/tuf_keys` #981cc @riyazdf @endophage