v0.106.1

Fixed

• Security: vk-registry refuses a pushed manifest that names anything but a lowercase sha256
  digest. A manifest or index whose config, layers, child manifests or subject name another
  digest, sha512: included, is refused with DIGEST_INVALID instead of being stored.
  Manifests the pull-through relay fetches from an upstream are kept as they come.
• Security: vk checks every digest a bundle pulled from a registry names before using it.
  A MICROVM_IMAGE, build-cache entry or Windows layer whose manifest names anything but a
  lowercase sha256: digest now fails to restore, with an error naming it, instead of being
  assembled from whatever the node's local cache holds under that name.
• Security: a blob stored by vk-registry always matches its digest. A chunk sent to a blob
  upload while the upload was being completed could change the stored blob after its digest
  was checked. Such a chunk is now refused, and the upload completes with the bytes it
  verified.

Full Changelog: v0.106.0...v0.106.1