conventional-changelog: Recent release of `@conventional-changelog/git-client` is causing a downstream issue with lerna version

πŸ‘‹πŸΌ Looks like a recent release of @conventional-changelog/git-client is causing a downstream issue with lerna version. See https://github.com/lerna-lite/lerna-lite/issues/1061 for details.

Managed to work around it by downgrading to @conventional-changelog/git-client@2.4.0

Including the error so it’s discoverable by search here:

Error: fatal: write failure on 'stdout': Connection reset by peer
    at catchProcessError (file:///home/runner/work/sanity/sanity/node_modules/.pnpm/@simple-libs+child-process-utils@1.0.0/node_modules/@simple-libs/child-process-utils/dist/index.js:34:17)
    at async throwProcessError (file:///home/runner/work/sanity/sanity/node_modules/.pnpm/@simple-libs+child-process-utils@1.0.0/node_modules/@simple-libs/child-process-utils/dist/index.js:43:19)

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Comments: 29 (10 by maintainers)

Most upvoted comments

Hi all. You can run pnpm up to upgrade to @simple-libs/child-process-utils@1.0.1 with issue fix.

Confirming the issue is fixed now. Thank you @dangreen!

@ghiscoding this code is equivalent. Just Promise.then/catch replaced with async/await syntax

https://github.com/lerna-lite/lerna-lite/issues/1062 @dangreen

This is all details from lerna-lite, the error was catched very soon after it’s being thrown out. Not sure lerna or here who catches it though.

Looks like we might have had a couple of instances where it ran successfully with conventional-changelog/git-client@2.5.0 yesterday – very odd. I’ll see if I can create a consistent and minimal repro.