[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
node-pty	1.2.0-beta.17 → 1.2.0-beta.18

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • 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 was generated by Mend Renovate. View the repository job log.

[dex4er]

@claude Analyze changes in this update

[claude]

Claude finished @dex4er's task in 1m 23s —— View job

---

Analysis: node-pty 1.2.0-beta.17 → 1.2.0-beta.18

• Read the PR diff
• Compare the upstream changes between beta.17 and beta.18
• Check how Freelens uses node-pty
• Post the analysis

Verdict: safe to merge. beta.18 has the same code as beta.17. Only the version string changed, and the macOS and Windows prebuilds were compiled again with the same code.

What this PR changes

• pnpm-workspace.yaml: the catalog pin goes from 1.2.0-beta.17 to 1.2.0-beta.18.
• pnpm-lock.yaml: the catalog entry, both importers (freelens, packages/core) and the integrity hash move with it. node-addon-api stays at 7.1.1, and the dependency set and install scripts are unchanged.

Upstream changes

node-pty doesn't tag its betas, so I lined up the npm publish times with the commits on microsoft/node-pty main. beta.17 was published 2026-10-22 20:13 UTC and beta.18 six hours later, at 2026-10-23 02:47 UTC. The commits merged in between change only the release process:

• Use npm 11.6.3 for Azure Artifacts publishing microsoft/node-pty#1002: the publish pipeline uses npm 11.6.3 to publish to Azure Artifacts (one line in publish.yml).
• Clarify which registry determines beta versions microsoft/node-pty#1003: a comment in scripts/increment-version.js explaining how the next beta number is picked.

Neither file is in the npm package. beta.18 looks like a re-publish once the new npm version was in the pipeline.

Package contents compared (jsDelivr per-file SHA-256)

Files	Result
lib/**/*.js, typings/node-pty.d.ts, src/**, binding.gyp, scripts/*.js, README.md, LICENSE	identical
package.json	only version differs (checked against the installed beta.18)
third_party/conpty/1.25.260303002/* and prebuilds/win32-*/conpty/{conpty.dll,OpenConsole.exe}	identical (same Microsoft ConPTY build)
prebuilds/linux-{x64,arm64}/pty.node	identical
prebuilds/darwin-*/{pty.node,spawn-helper}	different hash, same size: compiled again
prebuilds/win32-*/{conpty.node,conpty_console_list.node} and .pdb	different hash, same size, except win32-arm64/conpty_console_list.pdb (+8 KiB, which accounts for the whole difference in unpackedSize)

The JavaScript and the C++ sources are byte-identical, so the rebuilt .node and spawn-helper files differ only in build details: timestamps, code signatures and PDB GUIDs. Their behaviour stays the same. The typings are identical too, so spawn-pty.injectable.ts, shell-session.ts and the Pty re-export in packages/core/src/main/library.ts keep the same API.

Freelens-specific points

• freelens/electron-builder.yml filters on prebuilds/${platform}-${arch}, build/ and third_party/. The package layout hasn't changed, so those filters still match.
• The bundled ConPTY (conpty.dll / OpenConsole.exe), which release.yaml checks under app.asar.unpacked/.../conpty, is byte-identical to the beta.17 copy.
• The Windows and macOS binaries in the release artifact will have new hashes. That's expected from the rebuild, and the release scans will just see new hashes for the same code.
• .renovaterc.json applies deb versioning to node-pty, so Renovate does treat beta.17 → beta.18 as an upgrade.

CI

Every check on this PR passes: unit tests (4 shards), type check, knip, licenses, DI registration, Trunk, npm dedupe, and integration tests on macOS 26, Ubuntu 24.04 arm64 and Windows 2025. The integration tests run the terminal on the new prebuilds. I didn't run anything locally, because the CI results already cover it.
| Model: claude-opus-5-5[1m]