You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've noticed, that the Travis-CI builds are failing, since Aug,8th.
When I've created my pull request (#256),
my build was also failing, but it wasn't my fault. Sure, everyone will say this ;-)
But, all tests are running fine on my machine.
I've googled a while and found this travis-ci/travis-ci#2654
So, it seems shields isn't alone. IMHO, the root cause is this bruce/node-temp@980b92f
Via node module 'ass' there is a dependency to 'temp-0.6.0'.
Newer version 'temp-0.8.1' fixes the problem.
To make a long story short, I've did a pull-request to module 'ass', see lloyd/ass#10
If this will accepted and released to an updated version,
shields should update its dependencies, too.
Thus, everything will shine and work again, IMHO.
Feedback and support is welcome.
Best Regards
Martin
PS: Frankly said, I just wanted to have Maven Central supported ;-) (#256)
The text was updated successfully, but these errors were encountered:
Hi,
I've noticed, that the Travis-CI builds are failing, since Aug,8th.
When I've created my pull request (#256),
my build was also failing, but it wasn't my fault. Sure, everyone will say this ;-)
But, all tests are running fine on my machine.
I've googled a while and found this travis-ci/travis-ci#2654
So, it seems shields isn't alone. IMHO, the root cause is this bruce/node-temp@980b92f
Via node module 'ass' there is a dependency to 'temp-0.6.0'.
Newer version 'temp-0.8.1' fixes the problem.
To make a long story short, I've did a pull-request to module 'ass', see lloyd/ass#10
If this will accepted and released to an updated version,
shields should update its dependencies, too.
Thus, everything will shine and work again, IMHO.
Feedback and support is welcome.
Best Regards
Martin
PS: Frankly said, I just wanted to have Maven Central supported ;-) (#256)
The text was updated successfully, but these errors were encountered: