GET image endpoint path param renamed from imageId to imageIdOrDigest
This is a breaking change — integrations that rely on the affected behaviour will need updates before the change rolls out.
What changed
The GET /v1/vcr/repository/{idOrName}/images/{imageId} endpoint has been split: the GET operation now lives at /v1/vcr/repository/{idOrName}/images/{imageIdOrDigest} with the path parameter renamed from imageId to imageIdOrDigest, while the DELETE operation remains at the original {imageId} path. Any client constructing the GET URL with the old path template {imageId} will now hit a non-existent route, and the parameter name change may break SDK/code that references the parameter by name. The description update also documents that the new parameter accepts either an internal id (image_...) or a manifest digest (sha256:...).