Bad release for 3.1.3

[fpavageau]

Bad release for 3.1.3

[edwinyoung]

Adding error message to this:

npm ERR! code ENOENT
npm ERR! syscall spawn git
npm ERR! path git
npm ERR! errno ENOENT
npm ERR! enoent Error while executing:
npm ERR! enoent undefined ls-remote -h -t ssh://[email protected]/apigee/microgateway-config.git
npm ERR! enoent
npm ERR! enoent
npm ERR! enoent spawn git ENOENT
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

[edwinyoung]

Want to add that running git ls-remote -h -t ssh://[email protected]/apigee/microgateway-config.git on my local machine works just fine, but npm seems to be failing on this command for a reason I can't determine.

[nairpraving]

Agree, I am seeing the same issue, also migrating to buster from alpine, so this email helped. else I would have gone into a rabbit hole.

…

On Thu, Apr 16, 2020, 1:04 PM Ed Young ***@***.***> wrote: Want to add that running git ls-remote -h -t ssh:// ***@***.***/apigee/microgateway-config.git on my local machine works just fine, but npm seems to be failing on this command for a reason I can't determine. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#284 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGK7QS2UTX5HMZNPKUVSY6TRM43C5ANCNFSM4MJN7WQA> .

[atoom]

Same issue for us!

I have opened a ticket with Apigee support - hopefully they will get someone from the development team to look at this.

[keyurkarnik]

Installing git on the target machine solves the issue. That is not a fix, but a workaround

[keyurkarnik]

Deprecated version 3.1.3.
Replaced with version 3.1.4

This issue was caused by core pulling in an incorrect dependency. The issue gets manifested only when git is not available on the target machine.