fix: write explicit newline when updating Electron package version in release workflow

[mahata]

The Electron release workflow switched from pnpm version to an inline Node update to avoid lifecycle-script side effects, but review feedback flagged newline handling in the JSON write path. This PR tightens that step to ensure electron/package.json is always written with a real trailing newline.

• Workflow update (.github/workflows/electron-release.yml)
  • Adjusted the inline Node write expression in Update electron package version to append an explicit newline character via String.fromCharCode(10).
  • Keeps the no-lifecycle-script behavior while removing ambiguity around escape handling in the one-liner.

run: node -e "const fs=require('fs');const p=JSON.parse(fs.readFileSync('electron/package.json','utf8'));p.version=process.env.VERSION;fs.writeFileSync('electron/package.json',JSON.stringify(p,null,2)+String.fromCharCode(10))"

[Copilot]

Pull request overview

Updates the Electron release GitHub Actions workflow to bump the Electron package version without invoking pnpm version (and its lifecycle scripts), preventing Electron from being launched during CI versioning.

Changes:

• Replace pnpm --dir electron version ... with a node -e script that directly updates electron/package.json.
• Remove the explicit shell: bash from the “Update electron package version” step.

Show a summary per file

File	Description
.github/workflows/electron-release.yml	Adjusts the Electron release workflow to update electron/package.json version via Node to avoid lifecycle script execution in CI.

Copilot's findings

• Files reviewed: 1/1 changed files
• Comments generated: 1

[Copilot]

The Node script appends '\\n' to the JSON output, which writes a literal backslash + n at the end of electron/package.json and makes the file invalid JSON. Append a real newline instead (use \n in the JS string literal, not \\n).

[mahata]

@copilot apply changes based on this feedback

[Copilot]

Updated in a161e9d: the workflow now appends a real newline explicitly via String.fromCharCode(10) in the Node version-update step, so electron/package.json remains valid JSON.