git push failed when using SSH key with passphrase

[wohenbushuang]

Describe the bug

When using SSH key with passphrase, git push to github will be jammed, and there is no passphrase prompt shown.

In terminal:

>npm run release

> ***********@0.3.4 release
> *********** release


i No commits since the last version

√ Current version 0.3.4 »     pre-patch 0.3.5-beta.1

   files package-lock.json
         package.json
  commit chore(publish): release v0.3.5-beta.1
     tag v0.3.5-beta.1
    push yes

    from 0.3.4
      to 0.3.5-beta.1

√ Bump? ... yes
 ✔ Updated package-lock.json to 0.3.5-beta.1
 ✔ Updated package.json to 0.3.5-beta.1
 ✔ Git commit
 ✔ Git tag

When only git push manually, there is no problem:

>git push origin v0.3.4
Enter passphrase for key 'C:\Users\admin/.ssh/id_rsa':
Enumerating objects: 1, done.
Counting objects: 100% (1/1), done.
Writing objects: 100% (1/1), 170 bytes | 170.00 KiB/s, done.
Total 1 (delta 0), reused 0 (delta 0), pack-reused 0 (from 0)
To github.com:**************/***********.git
 * [new tag]         v0.3.4 -> v0.3.4

Reproduction

maybe it is irrelevant with a specific project code

System Info

System:
    OS: Windows 10 10.0.19045
    CPU: (20) x64 13th Gen Intel(R) Core(TM) i5-13600K
    Memory: 43.99 GB / 63.75 GB
  Binaries:
    Node: 22.14.0 - C:\Program Files\nodejs\node.EXE
    npm: 8.5.5 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 135.0.7049.115
    Edge: Chromium (135.0.3179.85)
    Internet Explorer: 11.0.19041.4355

Used Package Manager

npm

Validations

• Follow our Code of Conduct
• Read the Contributing Guide.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
• The provided reproduction is a minimal reproducible of the bug.

Contributions

• I am willing to submit a PR to fix this issue
• I am willing to submit a PR with failing tests (actually just go ahead and do it, thanks!)