Support GPG password prompt

[bunysae]

Fixes #79 the gpg-password-prompt is gobbled. The listr-task "Bumping version using npm" gets a suspend-flag, which stops the listr-update-renderer.

In order to get this solution working, there are same changes necessary at listr and listr-update-renderer.
The pull-requests for this changes can be found at the following links:

• listr
• listr-update-renderer

Testing this pull-request requires the following client-setup:

1. create a gpg-key-pair with the command gpg --generate-key
2. set this key as default key for commit-signing with the command git config --set --global user.signingkey <KEY>
3. activate commit-signing:

• for npm with the command npm config set sign-git-commit true or
• for yarn with the command yarn config set version-sign-git-tag true

---

IssueHunt Summary

[sindresorhus]

The pull-requests for this changes are currently open.

Can you link to those pull requests?

[sindresorhus]

What about Yarn? Look at the task above the one you modified.

[sindresorhus]

Can you give the PR a better title?

[bunysae]

When using yarn, the gpg-password-prompt was also gobbled. I fixed it with the last commits.

[sindresorhus]

Can you mention this feature in the readme?

[bunysae]

Can you mention this feature in the readme?

It's mentioned.

[sindresorhus]

Maybe we could move this forward by retargeting your PRs to https://github.com/cenk1cenk2/listr2 and then move to listr2 in np.