[pull] main from electron:main

[pull]

See Commits and Changes for more details.

---

Created by pull[bot]

Can you help keep this open source service alive? 💖 Please sponsor : )

[commit-lint]

Documentation

• Update timeline for E15 alpha announcement (docs: Update timeline for E15 alpha announcement electron/electron#30109) (eb2efd4)
• add 'did-attach' event documentation (docs: add <webview> 'did-attach' event documentation electron/electron#29899) (c0995b8)
• fix fiddle path (docs: fix fiddle path electron/electron#30139) (a855aa3)
• add runtime.reload as supported extension api (docs: add runtime.reload as supported extension api electron/electron#29925) (b2da2f7)
• update supported versions to match new release cadence (docs: update supported versions to match new release cadence electron/electron#30121) (4b780f9)
• Ffx broken context isolation link in sandbox docs (docs: fix broken context isolation link in sandbox docs electron/electron#30177) (9441ff7)
• update default branch for Electron Packager API links (docs: update default branch for Electron Packager API links electron/electron#30175) (a329842)
• mention sandboxing in security docs (docs: mention sandboxing in security docs electron/electron#30147) (d35fb2a)

Chore

• update releases to 8 weeks in CONTRIBUTING (chore: update releases to 8 weeks in CONTRIBUTING electron/electron#30115) (1897b14)
• bump node to v16.5.0 (main) (chore: bump node to v16.5.0 (main) electron/electron#30031) (063ac19)
• remove unused getWebPreferences method (chore: remove unused getWebPreferences method electron/electron#30160) (612361c)

Features

• expose location and modifiers on before-input-event (feat: expose location and modifiers on before-input-event electron/electron#29850) (4d0475c)
• add signal option to dialog.showMessageBox (feat: add signal option to dialog.showMessageBox electron/electron#26102) (05ba635)
• support crashpad on linux (feat: support crashpad on linux electron/electron#29719) (c9ba0d0)

Bug Fixes

• pressing ESC should exit fullscreen from webview (fix: pressing ESC should exit fullscreen from webview electron/electron#30063) (637ba48)
• use correct userData path when unbundled (fix: use correct userData path when unbundled electron/electron#30113) (bec47f5)
• double traffic lights on exit fullscreen (fix: double traffic lights on exit fullscreen electron/electron#30114) (3f38681)
• handle redirects within registered protocols (fix: handle redirects within registered protocols electron/electron#29796) (341b370)
• BrowserWindow transparency not working (fix: BrowserWindow transparency not working electron/electron#30136) (1bb689e)
• allow colored tray titles when font type is specified (fix: allow colored tray titles when font type is specified electron/electron#30146) (0d9e6f2)

Spec

• disable flaky fullscreen test (test: disable flaky fullscreen test electron/electron#30141) (4931c05)

Build System

• update version-bumper to support alpha (build: update version-bumper to support alpha electron/electron#30165) (deb75ce)
• handle release failure by existing with code 1 (build: handle release failure by exiting with code 1 electron/electron#30216) (9fe70c5)

Contributors

sofianguy, VerteDinde, nornagon, zcbenz, miniak, Davenury, electron-bot, molant, deepak1556, utkarsh-dixit, georgexu99, codebytere, dsanders11, electron-roller[bot], jota11, malept, MarshallOfSound

Commit-Lint commands

You can trigger Commit-Lint actions by commenting on this PR:

• @Commit-Lint merge patch will merge dependabot PR on "patch" versions (X.X.Y - Y change)
• @Commit-Lint merge minor will merge dependabot PR on "minor" versions (X.Y.Y - Y change)
• @Commit-Lint merge major will merge dependabot PR on "major" versions (Y.Y.Y - Y change)
• @Commit-Lint merge disable will desactivate merge dependabot PR
• @Commit-Lint review will approve dependabot PR
• @Commit-Lint stop review will stop approve dependabot PR

[pull-request-quantifier-deprecated]

This PR has 8588 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Large
Size       : +5581 -3007
Percentile : 100%

Total files changed: 375

Change summary by file extension:
.yml : +49 -7
.md : +424 -218
.json : +108 -14
.sh : +55 -0
.gitignore : +1 -0
.nvmrc : +1 -0
.gn : +37 -46
.json5 : +3 -1
.py : +28 -6
.gni : +41 -10
.cc : +1701 -659
.grdp : +13 -0
.ts : +862 -555
.js : +232 -104
.patches : +13 -3
.patch : +1436 -1004
.manifest : +4 -0
.h : +342 -164
.idl : +0 -20
.mm : +200 -174
.rc : +4 -4
.html : +4 -0
.txt : +20 -15
DEPS : +2 -2
ELECTRON_VERSION : +1 -1

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detetcted.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.