fix(deps): update dependency node-pty-prebuilt-multiarch to ^0.10.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
node-pty-prebuilt-multiarch	^0.9.0 -> ^0.10.0

---

Release Notes

oznu/node-pty-prebuilt-multiarch

v0.10.0

Compare Source

---

Renovate configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by WhiteSource Renovate. View repository job log here.

[the-j0k3r]

[UziTech]

I made this update a breaking change so people will hopefully know what to expect. 😅

[github-actions]

🎉 This PR is included in version 13.0.0 🎉

The release is available on:

• GitHub release
• Atom package

Your semantic-release bot 📦🚀

[the-j0k3r]

I made this update a breaking change so people will hopefully know what to expect. 😅

Should just work ™️ famous last words. =)

[UziTech]

Ya the only issue should be when someone tries to update while still having x-terminal open in atom.

[the-j0k3r]

That breaks the update and thus expect dragons, frozen install at terminal-name\node_modules, maybe there should be some logic that closes x-terminal when you click update in atom.

Maybe not so trivial.

[UziTech]

I wonder if updating or uninstalling from atom deactivates the package first?

Answer: nope.

[the-j0k3r]

Answer: nope.

Yep its the bane of addons. Probably easier to intercept update call and do it that way, else APM needs to be fixed. That last is less likely to happen any time in the next 500 years. So get your vamp on =)

[the-j0k3r]

So heres whats happened on last upgrade 12.x to 13.x.

1. I closed all terminals and restarted atom, this to ensure terminals arent active anywhere.
2. triggered the update via Atom for the terminal
3. observed `~.atom\packages\x-terminal contents removed and waited for about 1 minute
4. node_modules appears and progress seems to stay there forever (waited 5 minutes)
5. got fed up with waiting and closed Atom
6. observed ~\.atom\packages\x-terminal contents re-appear

Upon examination the upgrade was successful, terminal works.