Fixing sigstore update

Author: kakabisht

docs/05.policy/03.admission/01.sigstore/01.sigstore.md

@@ -9,6 +9,10 @@ slug: /policy/admission/sigstore
 
 NeuVector enables a user to perform signature verification logic by integrating image signatures generated by Sigstore's cosign tool.
 
+:::note
+NeuVector currently supports scanning image signatures generated with cosign v2 only. Signatures created with cosign v3 do not trigger Sigstore verification.
+:::
+
 The following is an example of an admission control configuration that requires a deployment's image be signed by an appropriate key or identity.
 
 First, configure a root of trust. This can either be a public or private root of trust, depending on the Sigstore deployment used to generate signatures. If you have deployed your own instances of Sigstore's services, select the private root of trust option.

versioned_docs/version-5.2/05.policy/03.admission/01.sigstore/01.sigstore.md

@@ -9,6 +9,10 @@ slug: /policy/admission/sigstore
 
 NeuVector enables a user to perform signature verification logic by integrating image signatures generated by Sigstore's cosign tool.
 
+:::note
+NeuVector currently supports scanning image signatures generated with cosign v2 only. Signatures created with cosign v3 do not trigger Sigstore verification.
+:::
+
 The following is an example of an admission control configuration that requires a deployment's image be signed by an appropriate key or identity.
 
 First, configure a root of trust. This can either be a public or private root of trust, depending on the Sigstore deployment used to generate signatures. If you have deployed your own instances of Sigstore's services, select the private root of trust option.

versioned_docs/version-5.3/05.policy/03.admission/01.sigstore/01.sigstore.md

@@ -9,6 +9,10 @@ slug: /policy/admission/sigstore
 
 NeuVector enables a user to perform signature verification logic by integrating image signatures generated by Sigstore's cosign tool.
 
+:::note
+NeuVector currently supports scanning image signatures generated with cosign v2 only. Signatures created with cosign v3 do not trigger Sigstore verification.
+:::
+
 The following is an example of an admission control configuration that requires a deployment's image be signed by an appropriate key or identity.
 
 First, configure a root of trust. This can either be a public or private root of trust, depending on the Sigstore deployment used to generate signatures. If you have deployed your own instances of Sigstore's services, select the private root of trust option.

versioned_docs/version-5.4/05.policy/03.admission/01.sigstore/01.sigstore.md

@@ -9,6 +9,10 @@ slug: /policy/admission/sigstore
 
 NeuVector enables a user to perform signature verification logic by integrating image signatures generated by Sigstore's cosign tool.
 
+:::note
+NeuVector currently supports scanning image signatures generated with cosign v2 only. Signatures created with cosign v3 do not trigger Sigstore verification.
+:::
+
 The following is an example of an admission control configuration that requires a deployment's image be signed by an appropriate key or identity.
 
 First, configure a root of trust. This can either be a public or private root of trust, depending on the Sigstore deployment used to generate signatures. If you have deployed your own instances of Sigstore's services, select the private root of trust option.