You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The baked artifact doesn't contain artifactType field, which is not compliant to the OCI artifact guidance.
We still allow the above behavior to avoid breaking change in 1.* versions. The workaround is to set the default value of --image-spec to auto, when --artifact-type is not provided, switch to v1.0 automatically.
In v2 we should
Remove the auto switch: set the default value of --image-spec to v1.1
Ban the behavior and user need to use --image-spec v1.0 --config xxx to bake v1.0 OCI artifacts (without artifactType) explicitly.
The text was updated successfully, but these errors were encountered:
Historically ORAS user is able to push an artifact with pre-baked config data:
The baked artifact doesn't contain
artifactType
field, which is not compliant to the OCI artifact guidance.We still allow the above behavior to avoid breaking change in
1.*
versions. The workaround is to set the default value of--image-spec
toauto
, when--artifact-type
is not provided, switch tov1.0
automatically.In
v2
we should--image-spec
tov1.1
--image-spec v1.0 --config xxx
to bake v1.0 OCI artifacts (withoutartifactType
) explicitly.The text was updated successfully, but these errors were encountered: