[MM-67757] Upgrade to Electron v40.8.4

[devinbinnie]

Summary

Upgrade to Electron v40.8.4 to address a bug in Electron

Ticket Link

https://mattermost.atlassian.net/browse/MM-67757

Upgrade to Electron v40.8.4

Change Impact: 🟢 Low

Reasoning: This is a patch-level version bump (40.6.0 → 40.8.4) within the same minor version, containing only bug fixes per semantic versioning. The change is isolated to a single dependency with no modifications to application code, configuration, or scripts.

Regression Risk: Minimal. Patch updates to Electron are designed to be backward compatible and contain only bug fixes and security improvements. The codebase only references the Electron version for reporting and diagnostic purposes (Sentry error tracking and e2e test reporting), not for conditional logic or feature detection that could break.

QA Recommendation: Standard automated test suite execution is sufficient. Manual QA is not required given the isolated, backward-compatible nature of patch updates. However, basic smoke testing (app launch, basic navigation, platform-specific features) on supported platforms would be prudent due to Electron being the application framework.

---

Release Notes

Upgrade to Electron v40.8.4

[coderabbitai]

📝 Walkthrough

Walkthrough

The electron development dependency in package.json was updated from version 40.6.0 to 40.8.4. No other configuration, scripts, or dependencies were modified.

Changes

Cohort / File(s)	Summary
Dependency Update package.json	Updated electron dev dependency from 40.6.0 to 40.8.4

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 3

✅ 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 identifies the main change: upgrading Electron from v40.6.0 to v40.8.4, which is the only modification in the pull request.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch MM-67757

---

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

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@package.json`:
- Line 133: Update the electron dependency version in package.json from "40.8.4"
to the valid released version "40.8.3" so installs won't fail; locate the
"electron" entry in package.json and replace the version string accordingly (no
other code changes needed).

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 67b799ae-e281-424f-928b-7ae386d51cc6

📥 Commits

Reviewing files that changed from the base of the PR and between b662e83 and 0440db7.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (1)

• package.json

[mattermost-build]

Cherry pick is scheduled.