https://github.com/verdaccio/monorepo/blob/9.x/core/types/index.d.ts defines

type AuthAccessCallback = (error: string | null, access: boolean) => void;

interface IPluginAuth<T> extends IPlugin<T> {
  authenticate(user: string, password: string, cb: AuthCallback): void;
  adduser?(user: string, password: string, cb: AuthCallback): void;
  changePassword?(user: string, password: stri

Yeah, to be totally honest, I already thought we did this! 😅 This is the intended behavior, so we'll need to fix that. Thanks for reporting!

Originally posted by @simskij in containrrr/watchtower#647 (reply in thread)

I wish I could see stdout while Custom command is running.
https://github.com/skpm/skpm/blob/master/docs/notarization.md

Docker has this for pull: https://docs.docker.com/engine/reference/commandline/pull/

The tarball format supports multiple images/tags. We'd just want to pull every tag for crane but with gcrane we could pull all the untagged manifests as well.

Docker doesn't have it for push but I don't see a reason not to support it.

This would work well with an --oci flag to do an image layout ins

The current install docs are a bit all over the place:

• The kustomize install instructions are under the install directory but the Helm instructions are under docs. I guess the best solution is to move the kustomize instructions but leave a placeholder in install pointing to the docs guide.
• The Helm instructions could do with a bit more context and explanation, especially on TLS ingr

To repro the issue use an image that is not fully qualified as seen below.

 1 ❯ oras push test:test .
panic: runtime error: slice bounds out of range

goroutine 1 [running]:
github.com/deislabs/oras/vendor/github.com/containerd/containerd/reference.Spec.Hostname(0xc000022bb0, 0x9, 0x0, 0x0, 0x147b544, 0xc0001db788)
...

As we always have one root-hash available for the registry we currently have cached, we can also set a DNS record (_dnslink.npm.open-registry.dev) to that value, and have any IPFS gateway being able to fetch the content.

Essentially, we just have to on every change to the registry hash, update a DNS TXT record for this to work.