Christoph Gysin

``` $ du -sh deno 159M deno ```

Sure: https://deno.land/status/6040c0d3000e775d008ff687 (still ongoing)

I have published v3.6.1.0 shortly before, could it be that both runs were competing for my 200Mb quota?

The webhook status reports: ``` Status: Error: Failed to clone git repository https://github.com/christophgysin/aws-sdk-js-v3 at tag v3.7.0.0 ``` But the module seems to have been published: https://deno.land/x/[email protected]

Sure, I will publish 3.7.0.1 later today.

Published 3.7.0.1, same result: https://deno.land/status/6040dad90060a69400416472 ``` Status: Error: Failed to clone git repository https://github.com/christophgysin/aws-sdk-js-v3 at tag v3.7.0.1 ```

Are these two separate issues? Should I open a new issue for "Failed to clone git repository"?

FYI: I just pushed 3.8.0.0, and got: https://deno.land/status/6044d72800add12b00d5f15f ``` Status: Success: Published module. Failed to run dependency analysis v2. ```

This is good enough for me. One somewhat related question though: I have since published 3.1.0.0 sucessfully. If I were now to redeliver 3.0.0.1, will that show up as the...

Hi @jputcu, I'll happily accept merge requests, and will try to answer any questions you might have.