chore: Update Electron version to 39.2.3

[jeanfbrito]

• Upgraded Electron dependency from version 37.6.0 to 39.2.3 to ensure compatibility with the latest features and improvements.
• Updated corresponding entries in yarn.lock to reflect the new Electron version.

https://rocketchat.atlassian.net/browse/SUP-929

Summary by CodeRabbit

• Chores
  • Updated Electron development dependency to version 39.2.3.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Electron devDependency version updated from 37.6.0 to 39.2.3 in package.json. No logic changes, API modifications, or configuration adjustments.

Changes

Cohort / File(s)	Change Summary
Dependency Version Bump package.json	Electron devDependency bumped from 37.6.0 to 39.2.3

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• No logic changes; purely a version constraint update in dependencies
• Review should verify version compatibility and check release notes if needed

Possibly related PRs

• chore(dev): bump electron to 37.6.0 #3109: Previous Electron version bump in the same file—related dependency management for the same package.

Poem

🐰 Electron's march to thirty-nine,
A minor bump, but oh so fine!
From thirty-seven, swift we'll hop,
New features flow without a stop!

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically describes the main change: updating the Electron version from 37.6.0 to 39.2.3, which matches the actual changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch update-electron-v39

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

• Jira integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between e457303 and 70e7f95.

⛔ Files ignored due to path filters (1)

• yarn.lock is excluded by !**/yarn.lock, !**/*.lock

📒 Files selected for processing (1)

• package.json (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)

• GitHub Check: check (windows-latest)
• GitHub Check: check (macos-latest)
• GitHub Check: check (ubuntu-latest)

🔇 Additional comments (1)

package.json (1)

116-116: Verify compatibility and breaking changes for Electron 37.6.0 → 39.2.3 upgrade.

This is a significant 2-major-version jump. Electron major version bumps typically introduce breaking changes affecting APIs, native modules, and build tooling. The PR summary indicates no logic or configuration changes, which seems inconsistent with such a large version jump.

Please verify the following before merge:

1. Breaking changes: Review Electron's release notes for v38 and v39 to confirm no breaking changes affect this codebase.
2. Testing confirmation: Confirm the application has been tested end-to-end with Electron 39.2.3 (e.g., builds successfully on all platforms: macOS, Windows, Linux).
3. electron-builder compatibility: Verify that electron-builder 26.0.3 is compatible with Electron 39.2.3.
4. Native dependencies: Confirm no rebuild is needed for native modules due to Node.js/ABI changes between v37 and v39.
5. yarn.lock review: The PR mentions yarn.lock was updated—ensure those changes are complete and contain no conflicts or duplicate entries.

Consider whether an incremental upgrade path (v37 → v38 → v39) with validation at each step would reduce risk, or if you've already validated that the jump is safe.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}