gsadmin/pulse
1
0
Fork 0
mirror of https://github.com/rcourtman/Pulse.git synced 2026-10-25 04:59:43 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: pin registry qualification OCI references

Browse Source 
PR #2049 fails the repository docs-link drift guard because its qualification references follow mutable upstream main. Bind both OCI references to the verified v1.1.1 commit without changing the runtime repair or weakening the guard.

Change-source: pulse-maintainer
This commit is contained in:
pulse-triage[bot]
2026-09-11 11:03:38 +01:00
parent 052286db23
commit 72809bc1cf
1 changed files with 3 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tests/qualification/registry-response/README.md
+3 -2
View File
@@ -35,8 +35,9 @@ authentication middleware. No credential or authorization acceptance is claimed.
`fetchManifest` requires a schema-2 manifest envelope (config digest or index `fetchManifest` requires a schema-2 manifest envelope (config digest or index
manifest array) before using a GET fallback body or its digest metadata. This manifest array) before using a GET fallback body or its digest metadata. This
is a minimal error-page discriminator, not full descriptor/cryptographic is a minimal error-page discriminator, not full descriptor/cryptographic
validation. See the [OCI manifest specification](https://github.com/opencontainers/image-spec/blob/main/manifest.md) validation. See the [OCI manifest specification](https://github.com/opencontainers/image-spec/blob/147f9c13cedb47a0c4d9a11a222961073d585877/manifest.md)
and [image index specification](https://github.com/opencontainers/image-spec/blob/main/image-index.md). and [image index specification](https://github.com/opencontainers/image-spec/blob/147f9c13cedb47a0c4d9a11a222961073d585877/image-index.md),
both pinned to OCI Image Specification v1.1.1.
Existing HEAD digest handling, credentials, TLS, cache intervals and HTTP Existing HEAD digest handling, credentials, TLS, cache intervals and HTTP
error handling remain unchanged. A failed check is not proof of an up-to-date error handling remain unchanged. A failed check is not proof of an up-to-date
image; consumers must retain the error field. No new UI state is introduced. image; consumers must retain the error field. No new UI state is introduced.