New release version

[corburn]

It's been a few years since the 1.0.0 release with many changes since. Is it possible to cut a stable release? I like the addition of the the Digester interface.

[AkihiroSuda]

SGTM, cc @opencontainers/go-digest-maintainers PTAL

[thaJeztah]

overall SGTM; there's one thing I was wondering the other day; when I made my PR (some time ago) to register the default algorithms automatically, that also included sha384 (as it "came with the package"), however the OCI spec doesn't list it (I think; on my phone right now), so I wonder if we should register it by default, or somehow make it optional;

go-digest/sha.go

Line 21 in 5d0a588

RegisterAlgorithm(SHA384, crypto.SHA384)

[thaJeztah]

(basically; it's easier to add these things, than to remove, once released)

[corburn]

@thaJeztah agreed a future release could add registering SHA384 by default.

[thaJeztah]

Hm, ok, so I had my wires crossed, and thought that before 084376b, the SHA-384 was not registered, but it already was (but could not be used by default, unless "crypto/sha512" was imported.

So removing SHA384 would be a breaking change (and require a major version bump (V2); #97 (comment)

I did open a PR to somewhat improve docs (recommended use / not use);

• unify algorithms in a single list, and improve documentation #98

And perhaps we should indeed consider to remove the "not recommended" algorithms from the default for a V2.0 (don't register SHA-512 and SHA-384 by default, and don't import "crypto/sha512")

[nimengliusha]

It's been a few years since the 1.0.0 release with many changes since. Is it possible to cut a stable release?