-
Notifications
You must be signed in to change notification settings - Fork 38
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
Adding deprecation flags for SEV components and bumping to 5.1 #253
base: main
Are you sure you want to change the base?
Conversation
8170fd6
to
0de11c9
Compare
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
Adding WIP flag, waiting for 5.0 release first |
Set to draft PR as well, so this can't be merged. |
As discussed, adding deprecation flags for SEV components, so that it can be removed in the next 6.0 release. Bumping to 5.1 so that people can still use 5.0.0 without compilation warnings if they are using SEV. Signed-off-by: DGonzalezVillal <[email protected]>
0de11c9
to
438a9fc
Compare
Can be merged now if we want this still |
@@ -4,9 +4,24 @@ | |||
//! | |||
//! These are primarily offered as a convenience measure to avoid making | |||
//! HTTP requests to AMD's servers. | |||
|
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.
You left a deprecated
note on this module in src/certs/mod.rs
. Why are these deprecation notes also needed?
Let's hold off on this until sev-5.0.0 is packaged for distros. Will revisit this at that point. |
As discussed, adding deprecation flags for SEV components, so that it can be removed in the next 6.0 release. Bumping to 5.1 so that people can still use 5.0.0 without compilation warnings if they are using SEV.