v0.3.0-alpha

Verifying the Release

In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

gpg --keyserver hkps://keyserver.ubuntu.com --recv-keys 187F6ADD93AE3B0CF335AA6AB984570980684DCC

Once you have his PGP key you can verify the release (assuming manifest-v0.3.0-alpha.txt and manifest-ViktorTigerstrom-v0.3.0-alpha.sig are in the current directory) with:

gpg --verify manifest-ViktorTigerstrom-v0.3.0-alpha.sig manifest-v0.3.0-alpha.txt

You should see the following if the verification was successful:

gpg: Signature made Mon Feb  5 14:56:06 2024 CET
gpg:                using EDDSA key 187F6ADD93AE3B0CF335AA6AB984570980684DCC
gpg: Good signature from "Viktor Tigerström <vtigerstrom@gmail.com>"

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

cat manifest-v0.3.0-alpha.txt

One can use the shasum -a 256 <file name here> tool in order to re-compute the sha256 hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

Finally, you can also verify the tag itself with the following command:

git verify-tag v0.3.0-alpha

Verifying the Release Timestamp

We have also started to timestamp the manifest file with OpenTimeStamps along with its signature. A new file is now included along with the rest of our release artifacts: manifest-ViktorTigerstrom-v0.3.0-alpha.sig.ots.

Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following command:

ots verify manifest-ViktorTigerstrom-v0.3.0-alpha.sig.ots

These timestamps should give users confidence in the integrity of this release even after the key that signed the release expires.

What's Changed

• build(deps): bump google.golang.org/grpc from 1.41.0 to 1.56.3 by @dependabot in #94
• build(deps): bump golang.org/x/net from 0.7.0 to 0.17.0 by @dependabot in #91
• build(deps): bump google.golang.org/grpc from 1.39.0 to 1.56.3 in /hashmailrpc by @dependabot in #93
• build(deps): bump go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc from 0.25.0 to 0.46.0 by @dependabot in #97
• build(deps): bump go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc from 0.28.0 to 0.46.0 in /cmd/wasm-client by @dependabot in #98
• build(deps): bump golang.org/x/net from 0.14.0 to 0.17.0 by @dependabot in #100
• build(deps): bump go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc from 0.28.0 to 0.46.0 in /mobile by @dependabot in #99
• build(deps): bump go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc from 0.25.0 to 0.46.0 by @dependabot in #101
• .golangci: update linter rules by @ellemouton in #92
• gbn+mailbox: cleanup & prefixed logger by @ellemouton in #90
• gbn: Sender side only packeting resend bug fix by @ViktorTigerstrom in #87
• multi: bump go version to 1.21 by @ellemouton in #102
• doc: update release notes by @ViktorTigerstrom in #80
• gbn: set resend timeout dynamically by @ViktorTigerstrom in #88
• Fix WASM-client disconnection error by @ViktorTigerstrom in #103

New Contributors

• @dependabot made their first contribution in #94

Full Changelog: v0.2.8-alpha...v0.3.0-alpha