chore: update ref to docs (🤖) - #1217
Conversation
Deploying electron-website with
|
| Latest commit: |
7cf6377
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://64e23e8e.electron-website.pages.dev |
| Branch Preview URL: | https://docs-update-to-81ef9c71111e2.electron-website.pages.dev |
There was a problem hiding this comment.
LGTM — mechanical, vendored docs sync with no functional code changes.
What was reviewed: the new initiatorOrigin documentation additions across download-item.md, protocol.md, protocol-request.md, web-request.md, and session.md; the frame argument additions to session.md's will-download/preconnect API History blocks; and the unrelated prose cleanups (tray.md, fuses.md, and the "Discord server" removal across tutorial pages). Checked that initiatorOrigin is consistently described as optional/nullable in prose across all five files it touches (typed as plain string (optional) per this doc set's existing convention for such fields, not a regression introduced by this change).
Extended reasoning...
Overview
This PR is an automated, docs-only vendoring sync (docs/latest, bumped via .sha) pulling in upstream Electron documentation changes. The substantive content is a new initiatorOrigin field/API documented across download-item.md, protocol.md, structures/protocol-request.md, web-request.md, and a new frame argument for two session events, plus several unrelated prose cleanups (tray.md, fuses.md wording fix, and removal of "Discord server" help sections replaced by narrower "Found a bug" sections across tutorial pages).
Security risks
None. This is pure markdown documentation with no executable code, build config, or dependency changes.
Level of scrutiny
Low. This is a mechanical, bot-generated sync of vendored docs mirroring an upstream commit; the CLAUDE.md conventions for API History blocks (fenced YAML inside HTML comments, added/deprecated maxItems 1, placement rules) are structural/stylistic and don't gate correctness of prose. The bug-hunting system reported zero findings, and one candidate issue (nullable typing of initiatorOrigin in protocol-request.md) was investigated and found to follow the existing documentation convention for such fields rather than being a defect introduced by this diff.
Other factors
The PR was already reviewed and approved by another reviewer (electron-pr-approver) shortly after the commit landed, consistent with my own read of the diff as a low-risk, mechanical change.
Automated PR to update the docs to the latest commit (81ef9c71111e2dc47042c079c6a86a8c1117080c)