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
1) Remove the auto switch: set the default value of --image-spec to v1.1
2) Ban the behavior and user need to use --image-spec v1.0 --config xxx to bake v1.0 OCI artifacts (without artifactType) explicitly.
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 1) Remove the auto switch: set the default value of--image-spec
tov1.1
2) Ban the behavior and user need to use--image-spec v1.0 --config xxx
to bake v1.0 OCI artifacts (withoutartifactType
) explicitly.