-
Notifications
You must be signed in to change notification settings - Fork 2.6k
manifest/schema1: mark docker manifest v2, schema 1 deprecated #3804
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
Conversation
oh! linters may fail on this if we still use any of these (in tests); I'll check if |
🎉 CI is happy (phew) |
Should probably add a comment here, too distribution/configuration/configuration.go Line 206 in ede90db
|
14ec4e4
to
40c5b96
Compare
Updated; also added a note to the documentation. |
40c5b96
to
1811ff5
Compare
Docker Image manifest v2, schema version 1 is deprecated since 2015, when manifest v2, schema version 2 was introduced (2e3f493). Users should no longer use this specification other than for backward compatibility. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
1811ff5
to
ff2bce2
Compare
@corhere ptal 🤗 |
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!
We might also want to consider logging a warning in the manifest handlers when we encounter a schema 1 image
I would really like us to remove schema 1 image support completely from here. |
Docker Image manifest v2, schema version 1 is deprecated since 2015, when manifest v2, schema version 2 was introduced (2e3f493 (#1068)).
Users should no longer use this specification other than for backward compatibility.
With this PR, all functions are highlighted as deprecated, and linters will trigger a deprecation warning when importing the package and when using any of these types or functions.