New Linux ARM binaries, improved logging, and a crash fix

• We added Linux ARM (v6, v7, and arm64v8) binaries to our release system. You'll find them on our release page from this version forward.
• We also fixed a crasher bug when a Sia download failed. We now output a helpful error message instead of crashing. But hopefully you'll never see it and all your Sia downloads will succeed!
• Lastly we added some more INFO log output to help with debugging issues for users.

Bug fix for bad HEAD

• fixes #56

Important object storage bug fix

We highly recommend all users to upgrade to this release.

We found and fixed a buffer closing bug that was corrupting most or all git object uploads to Sia Skynet. This release contains the fix. If you were having trouble cloning or fetching via dgit, it's highly likely that this bug was the problem. Try again with this version and let us know if you still have issues.

Bug fixes

This release contains a couple of bug fixes:

1. Actually default to "Y(es)" responses in dgit init if the user doesn't type anything.
2. Prompt for keychain password when SSH'd into a remote macOS host and GUI dialog boxes can't be displayed.

Fixed batch sizes for Tupelo transactions

This improves the reliability when pushing large numbers of git objects.

Another try to fix Homebrew version strings

Let's hope the 3rd time is a charm on this one...

Fix version string in Homebrew builds

In v0.0.8-alpha, the dgit version command in Homebrew builds output -dev which isn't very helpful nor a real version. This release will (hopefully) say v0.0.9-alpha when you run dgit version, even on Homebrew builds.

Big speed up; version command; SSH fix

This release improves upon v0.0.7-alpha in the following ways:

1. Big performance improvement by batching Tupelo transactions and uploading to Sia in parallel in the background.
2. Adds a dgit version command to print out the version you're running.
3. Partially fixes a bug when running dgit over an SSH connection to a remote macOS host where it would claim to have stored your private key in the remote system's keychain, but in fact it had not and subsequent dgit commands would not behave correctly. Now it slightly more helpfully prints out an error message and fails. If you run into this "User interaction is not allowed" error, simply run security -i unlock-keychain, enter your keychain password, and then try again.

Fix exit code on fetch

• Fix exit code on fetch (#30)

Bug fix

• Fix exit code on valid git push #26