mailgun-ruby-1.1.3.gem does not match published SHA about mailgun-ruby HOT 7 CLOSED

FYI I've replaced the .gem from the first gem push so the SHA for version 1.1.3 will match now. We're also going to look to fix the race condition.

from mailgun-ruby.

@mwpastore Thank you for the report! I'll look in to this asap.

from mailgun-ruby.

@pirogoeth the reason for the mismatch is that your Travis build tries to push the gem for every ruby version in your build matrix. 99 times out of 100 this doesn't cause a problem but looks like there might be a race condition in rubygems.org that two pushes at the same time will fail and the wrong build file gets put into the S3 bucket.

I'd suggest only pushing from one build to be on the safe side in future.

from mailgun-ruby.

@pixeltrix I figured that's what it was. I'll fix it asap. Thanks!

from mailgun-ruby.

Thank you both!

from mailgun-ruby.

@dwradcliffe Thanks!

from mailgun-ruby.

This is fixed in the deploy changes from #78

from mailgun-ruby.