#2 potential fix. from changelog: a gson exception was thrown on error responses from bitly. Just checking the status field for a value of 200 would break UserLinkSaveIntegrationTest where a 304 is returned along with a valid data field. So we first try to deserialize and only in case of error we will do a partial deserialize. There is a new field deserialize_error in the response to indicate that the data field will be null as a result of an error
bump to 0.7.1, fix #2