chore: Update Electron version to 39.2.5

[jeanfbrito]

• Upgraded Electron dependency from version 39.2.3 to 39.2.5 to incorporate the latest bug fixes and improvements.
• Updated corresponding entries in yarn.lock to reflect the new Electron version.

Summary by CodeRabbit

• Chores
  • Updated Electron to version 39.2.5

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

[coderabbitai]

Walkthrough

Updated the electron devDependency from version 39.2.3 to 39.2.5 in package.json. This is a patch-level version increment with no changes to source code or public exports.

Changes

Cohort / File(s)	Change Summary
Dependency Version Bump package.json	Updated electron devDependency from 39.2.3 to 39.2.5

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Verify the version bump is intentional and aligns with release notes for Electron 39.2.5
• Confirm no breaking changes in the patch update that would affect the application

Possibly related PRs

• chore: Update Electron version to 39.2.3 #3144 — Both PRs update the electron devDependency, with this PR further bumping from 39.2.3 to 39.2.5
• chore(dev): bump electron to 37.6.0 #3109 — Related electron devDependency version update in the same package.json file

Poem

🐰 A hop and a skip, a version so new,
Electron takes flight from 39-2-3 to 2-5, it's true!
Patch notes whisper of fixes so fine,
Our package hops forward—a well-timed design ✨

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 accurately describes the main change: updating Electron from 39.2.3 to 39.2.5, which is the only modification in the 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.2.6

---

📜 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 8ba4976 and d4839fe.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (1)

• package.json (1 hunks)

🧰 Additional context used

🧠 Learnings (1)

📚 Learning: 2025-09-26T19:24:21.364Z

Learnt from: CR
Repo: RocketChat/Rocket.Chat.Electron PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-09-26T19:24:21.364Z
Learning: Applies to {rollup.config.mjs,electron-builder.json,tsconfig.json,.eslintrc.json,jest.config.js} : Maintain and configure the project via the designated root config files for build, packaging, TypeScript, ESLint, and Jest

Applied to files:

• package.json

⏰ 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 (ubuntu-latest)
• GitHub Check: check (macos-latest)
• GitHub Check: check (windows-latest)

🔇 Additional comments (2)

package.json (2)

116-116: yarn.lock has been properly updated.

The yarn.lock file contains the electron@npm:39.2.5 entry, confirming the dependency has been correctly updated to reflect the new Electron 39.2.5 version in package.json.

---

116-116: Confirm the branch name discrepancy.

The PR branch references update-electron-v39.2.6, but package.json was updated to version 39.2.5. Confirm whether this is intentional or if the target version should be 39.2.6.

For context: Electron 39.2.5 is a stable release containing only bug fixes (Windows notification hang, menu-did-close, resize artifacts, devtools flicker) with no security vulnerabilities or breaking changes from 39.2.3.

---

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.}