Electron Releases

Description of Change

This is intended to effectively retire electron/electron-website-updater, which has served us well, but feels overly complex for what we really want these days.

Some of the additional complexity in electron/electron-website-updater comes from filtering push events on e/e to only look at active release branches. The rest of the complexity comes from watching push events and publishing any changes to docs/ on a release branch to the website immediately after merge. This is actually not really desirable behavior, as it means the website docs will be showing unreleased features, and the next release may not be for a week or two.

That discrepancy has potential to confuse developers, and the only real benefits we get are docs fixes and updates to other parts of our docs like docs/tutorials go live immediately, instead of being delayed until the next release is put out.

IMO, given the trade off of having unreleased features shown on the docs website for a week or two, and having docs fixes delayed by a week or two, I think the latter is the lesser evil.

If we're happy with making that change, the additional complexity goes away and the flow for updating the website docs collapses down to this simple workflow, and lets us retire electron/electron-website-updater. We just need to trigger a website doc update on each published release which is the latest release.

Checklist

• PR description included

Release Notes

Notes: none