bump version to v0.1.0

[warpfork]

Attempting to do this with tooling.

[marten-seemann]

The workflows first need to be deployed here. Please enable it in https://github.com/protocol/.github/blob/master/config.json

[warpfork]

(Should it pick this up after that, or do I need to close and reopen the PR to give it an event to notice?)

[marten-seemann]

You’ll need to trigger the event again, sonGH Actions can pick it up.

[github-actions]

Suggested version: v0.1.0
Comparing to: v0.0.16 (diff)

Changes in go.mod file(s):

diff --git a/go.mod b/go.mod
index 36ef559..1baf4b6 100644
--- a/go.mod
+++ b/go.mod
@@ -5,8 +5,10 @@ require (
 	github.com/minio/sha256-simd v1.0.0
 	github.com/mr-tron/base58 v1.2.0
 	github.com/multiformats/go-varint v0.0.6
+	github.com/spaolacci/murmur3 v1.1.0
 	golang.org/x/crypto v0.0.0-20210220033148-5ea612d1eb83
 	golang.org/x/sys v0.0.0-20210309074719-68d13333faf2 // indirect
+	lukechampine.com/blake3 v1.1.6
 )
 
 go 1.16

gorelease says:

# github.com/multiformats/go-multihash
## incompatible changes
MURMUR3_128: removed
## compatible changes
BLAKE3: added
MURMUR3X64_64: added
Multihash.HexString: added
Multihash.String: added

# github.com/multiformats/go-multihash/core
## compatible changes
BLAKE3: added
MURMUR3X64_64: added
SHA2_224: added
SHA2_384: added
SHA2_512_224: added
SHA2_512_256: added

# github.com/multiformats/go-multihash/register/blake3
## compatible changes
package added

# github.com/multiformats/go-multihash/register/murmur3
## compatible changes
package added

# github.com/multiformats/go-multihash/test/sharness/t0030-lib
## compatible changes
package added

# summary
Suggested version: v0.1.0

gocompat says:

"github.com/multiformats/go-multihash".MURMUR3_128 TopLevelDeclarationDeleted

[warpfork]

Changing the tag of the next version to "v0.1.0".

The tooling's suggestion that we should be bumping more than the last digit is correct.

I floated the idea of bumping all the way to "v0.17.0", to keep the "number" going "up", but those polled in slack found it more confusing than not, so...

Happy "v0.1.0", go-multihash!