Repository navigation
chore: update ref to docs (🤖) - #1260
MarshallOfSound merged 3 commits into
Conversation
Deploying electron-website with
|
| Latest commit: |
e7fa513
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://709b0533.electron-website.pages.dev |
| Branch Preview URL: | https://docs-update-to-54f961b44b83e.electron-website.pages.dev |
There was a problem hiding this comment.
Nothing blocking. The comments below are optional suggestions. There is no need to push a fix for them before merging.
Beyond the inline findings, I also checked whether the new experimental ses.registerLocalAIHandler() and localAIHandler APIs need API History blocks per docs/latest/CLAUDE.md's rules. Ruled out: other experimental APIs across this same doc tree (e.g. service-workers.md's getWorkerFromVersionID, startWorkerForScope) are likewise documented without history blocks, consistent with upstream not yet cutting a history entry for unreleased/experimental features rather than an omission specific to this sync.
Extended reasoning...
This is a purely mechanical vendored-docs sync (48 files under docs/latest, bumping docs/latest/.sha) touching no application or security-sensitive code, so the review focus was documentation accuracy against docs/latest/CLAUDE.md's API-History conventions. Two confirmed inline findings were posted: the new Local AI Handler pages are missing from sidebars.js navigation, and the newly added API History block on app.md's configureWebAuthn cites the wrong origin PR (#51563 instead of #51255 per blog/electron-43-0.md). I additionally checked whether the new experimental session/localAIHandler APIs were missing required history blocks and ruled that out as consistent with how other experimental APIs in the same tree are documented. Given the two confirmed findings, this should not be approved outright.
Automated PR to update the docs to the latest commit (54f961b44b83e4ece81065ab60a182fd0c38c01e)