From 60fc69c5ad8afb8ca35e96c78a3e64ca35d26f1d Mon Sep 17 00:00:00 2001 From: Brandon Mitchell Date: Thu, 27 Jul 2023 01:44:07 -0400 Subject: [PATCH] Rephrase the subject exclusion from validation (#445) Signed-off-by: Brandon Mitchell --- spec.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/spec.md b/spec.md index 439a7fc8..e4f86e21 100644 --- a/spec.md +++ b/spec.md @@ -206,9 +206,9 @@ If the blob or manifest is not found in the registry, the response code MUST be Pushing an object typically works in the opposite order as a pull: the blobs making up the object are uploaded first, and the manifest last. A useful diagram is provided [here](https://github.com/google/go-containerregistry/tree/d7f8d06c87ed209507dd5f2d723267fe35b38a9f/pkg/v1/remote#anatomy-of-an-image-upload). -A registry MAY reject a manifest of any type uploaded to the manifest endpoint if it references manifests or blobs that do not exist in the registry. A registry MUST accept an otherwise valid manifest with a `subject` field that references a manifest that does not exist, allowing clients to push a manifest and referrers to that manifest in either order. -When a manifest is rejected for these reasons, it MUST result in one or more `MANIFEST_BLOB_UNKNOWN` errors [code-1](#error-codes). +A registry MAY reject a manifest uploaded to the manifest endpoint with descriptors in other fields that reference a manifest or blob that does not exist in the registry. +When a manifest is rejected for this reason, it MUST result in one or more `MANIFEST_BLOB_UNKNOWN` errors [code-1](#error-codes). ##### Pushing blobs