v0.4.2

• Trace HTTP calls by passing GIT_CURL_VERBOSE=1 as an env var. #175
• Fix for cases where the push command cannot find the object in .git/hawser/objects. #176
• Update API specification #173 #174
• Stop resetting credentials on 404 responses #174
• Print to stderr when a file is being downloaded during clone or checkout. #180

v0.4.1

Bug fix release from Pre-Release feedback.

• Improved the Windows install script. #158
• Support for alternate remotes #154
• Nicer error message on 403/404 errors #165
• Support GET redirects #163
• Fixed bug with git hawser add when .gitattributes does not have a trailing linebreak. #168

v0.4.0

• Add git hawser add ... and git hawser rm ... commands.
• Fix for GitHub Enterprise 2.1

v0.3.6

Rename to Hawser.

v0.3.5

• Support disabling HTTPS verification with GIT_SSL_NO_VERIFY ENV or http.sslVerify git config.

v0.3.4

• Git media is better able to scan a repository history to find media files
• push uses the scanner to be more efficient
• Introduced a git media status command, analogous to git status to show the current state of git media files

v0.3.3

• GIT_MEDIA_PROGRESS variable should be an absolute path rather than a file:// URI #134

v0.3.2

• Fix a a lock file issue on Windows #131

v0.3.1

• If the pre-push hook is detected to be out of date, give a notification to run git media update #129

v0.3.0

• Make pushing git media files smarter #122 @rubyist

Note: This release reports as v0.2.3. It's recommended that you upgrade to v0.3.1 ASAP.

This release adds some smarts to pushing files to ensure that files aren't pushed multiple times, and only files actually in the commit(s) being pushed are sent to the git media server.

There are some changes with git media's internal bookeeping. If you have existing git media repositories cloned you should run git media update to ensure its database is up to date. If you're creating a new git media repository, or cloning an existing repository from GitHub you do not need to run the update command.