⬆️ Electron 11.5.0

[DeeDeeG]

Requirements for Contributing a Bug Fix (from template, click to expand):

• Fill out the template below. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion.
• The pull request must only fix an existing bug. To contribute other changes, you must use a different template. You can see all templates at https://github.com/atom/.github/tree/master/.github/PULL_REQUEST_TEMPLATE.
• The pull request must update the test suite to demonstrate the changed functionality. For guidance, please see https://flight-manual.atom.io/hacking-atom/sections/writing-specs/.
• After you create the pull request, all status checks must be pass before a maintainer reviews your contribution. For more details, please see https://github.com/atom/.github/tree/master/CONTRIBUTING.md#pull-requests.

Identify the Bug

#22687 (comment)

The existence of Electron 11.5.0 (the final release of the Electron 11.x series) was pointed out by @mfonville in the main Electron 11 upgrade PR. (See comment linked above). The bug is... We're out of date!

Description of the Change

Update Atom to use Electron 11.5.0 instead of 11.4.12. The only changes in this Electron release are a few security patches cherry-picked from newer Chromium and V8. See the release notes:

• https://www.electronjs.org/releases/stable?version=11#11.5.0
• https://github.com/electron/electron/releases/tag/v11.5.0

Alternate Designs

No alternatives were seriously considered. (I like security patches, and I lack the ability to whip up, say, an Electron 12 upgrade right now...)

Possible Drawbacks

Probably none. These are really small security patches, hopefully they aren't buggy patches... 👀

Verification Process

Tests pass in CI at my fork: https://dev.azure.com/DeeDeeG/b/_build/results?buildId=1233

(Please disregard the failed "UploadArtifacts" job, that's CI-specific and I don't think anyone has gotten that to pass on forks of the Atom repo yet -- that failing only means I'm not running CI on the official atom/atom repo.)

Release Notes

⬆️ Electron 11.5.0

[DeeDeeG]

Test failure is unrelated. It passed CI on my CI account, given enough chances to rerun. Failure appears to be, as usual, unrelated test failures that (unfortunately) happen sort of randomly on every branch.

I think it would be sensible to include this in 1.61-releases branch, because otherwise there will be 11.4.12 in the final Atom1.61... And Electron 11.5.0 just adds a few small security fixes cherry-picked from upstream Chromium and V8.

Consider merging, in order to get a few more security patches into Atom. Thanks.