Electron 团队很高兴地宣布 Electron 6.0.0 正式发布！你可以通过 npm 使用 npm install electron@latest 安装，或从我们的发布网站下载。本次发布包含了大量升级、修复和新功能。我们迫不及待想看看你会用它们构建什么！继续阅读以了解本次发布的详细信息，并请分享你任何的反馈！
🌐 The Electron team is excited to announce the release of Electron 6.0.0! You can install it with npm via npm install electron@latest or download it from our releases website. The release is packed with upgrades, fixes, and new features. We can't wait to see what you build with them! Continue reading for details about this release, and please share any feedback you have!
新功能
🌐 What's New
今天对 Electron 项目来说是一个里程碑：这是我们第一次在与对应的 Chrome 稳定版本 同一天 发布稳定的 Electron 版本！🎉
🌐 Today marks a first for the Electron project: this is the first time we've made a stable Electron release on the same day as the corresponding Chrome stable release! 🎉
Electron 的大部分功能由 Chromium、Node.js 和 V8 的核心组件提供。Electron 会跟进这些项目的最新进展，为用户提供新的 JavaScript 功能、性能改进和安全修复。在 Electron 6 中，这些软件包中的每一个都有一次主要版本更新：
🌐 Much of Electron's functionality is provided by the core components of Chromium, Node.js, and V8. Electron keeps up-to-date with these projects to provide our users with new JavaScript features, performance improvements, and security fixes. Each of these packages has a major version bump in Electron 6:
- Chromium
76.0.3809.88
- Node.js
12.4.0
- V8
7.6.303.22
此版本还包括对 Electron API 的改进。发行说明 提供了更完整的列表，但以下是主要亮点：
🌐 This release also includes improvements to Electron's APIs. The release notes have a more complete list, but here are the highlights:
Promisification
Electron 6.0 继续了在 5.0 中启动的现代化计划，以改进对Promise的支持。
🌐 Electron 6.0 continues the modernization initiative started in 5.0 to improve Promise support.
这些函数现在返回 Promises，并且仍然支持旧版基于回调的调用：
🌐 These functions now return Promises and still support older callback-based invocation:
contentTracing.getCategories() #16583contentTracing.getCategories() #16583contentTracing.getTraceBufferUsage() #16600contents.executeJavaScript() #17312cookies.flushStore() #16464cookies.get() #16464cookies.remove() #16464cookies.set() #16464dialog.showCertificateTrustDialog() #17181inAppPurchase.getProducts() #17355inAppPurchase.purchaseProduct()#17355netLog.stopLogging() #16862session.clearAuthCache() #17259session.clearCache() #17185session.clearHostResolverCache() #17229session.clearStorageData() #17249session.getBlobData() #17303session.getCacheSize() #17185session.resolveProxy() #17222session.setProxy() #17222webContents.hasServiceWorker() #16535webContents.printToPDF() #16795webContents.savePage() #16742webFrame.executeJavaScript() #17312webFrame.executeJavaScriptInIsolatedWorld() #17312webviewTag.executeJavaScript() #17312
这些函数现在有两种形式：同步和基于 Promise 的异步：
🌐 These functions now have two forms, synchronous and Promise-based asynchronous:
dialog.showMessageBox()/dialog.showMessageBoxSync() #17298dialog.showOpenDialog()/dialog.showOpenDialogSync() #16973dialog.showSaveDialog()/dialog.showSaveDialogSync() #17054
这些函数现在返回 Promises：
🌐 These functions now return Promises:
Electron Helper (Renderer).app、Electron Helper (GPU).app 和 Electron Helper (Plugin).app
🌐 Electron Helper (Renderer).app, Electron Helper (GPU).app and Electron Helper (Plugin).app
为了启用hardened runtime，它会限制可写执行内存以及加载由不同团队 ID 签名的代码，需要向 Helper 授予特殊的代码签名权限。
🌐 In order to enable the hardened runtime, which restricts things like
writable-executable memory and loading code signed by a different Team
ID, special code signing entitlements needed to be granted to the Helper.
为了将这些权限限制在需要它们的进程类型范围内，Chromium 添加了 三种新的 Helper 应用变体：一种用于渲染器（Electron Helper (Renderer).app）、一种用于 GPU 进程（Electron Helper (GPU).app）以及一种用于插件（Electron Helper (Plugin).app）。
🌐 To keep these entitlements scoped to the process types that require them, Chromium added
three new variants of the Helper app: one for renderers (Electron Helper (Renderer).app), one for the GPU process (Electron Helper (GPU).app) and one for plugins (Electron Helper (Plugin).app).
使用 electron-osx-sign 对 Electron 应用进行代码签名的用户不需要对构建逻辑进行任何更改。如果你使用自定义脚本为应用进行代码签名，应确保三个新的辅助应用已正确签名。
🌐 Folks using electron-osx-sign to codesign their Electron app shouldn't have to make any changes to their build logic.
If you're codesigning your app with custom scripts, you should ensure
that the three new Helper applications are correctly codesigned.
为了正确地使用这些新助手打包你的应用，你需要使用 electron-packager@14.0.4 或更高版本。如果你使用的是 electron-builder，你应该关注 这个问题 来跟踪对这些新助手的支持情况。
🌐 In order to package your application correctly with these new helpers you need to be using electron-packager@14.0.4 or higher. If you are using electron-builder you should follow this issue to track support for these new helpers.
重大变化
🌐 Breaking Changes
- 此版本开始为未来对在渲染进程中加载的本地 Node 模块要求其必须是 N-API 或 Context Aware 打下基础。此更改的原因是提高性能、增强安全性以及减少维护工作量。完整细节及拟定时间表请查看 此问题。预计此更改将在 Electron v11 中完成。
net.IncomingMessage 头部已经略有更改，以更接近 Node.js 的行为，特别是 set-cookie 的值以及如何处理重复的头部。＃17517。shell.showItemInFolder() 现在返回 void，并且是一个异步调用。#17121- 应用现在必须在使用
app.getPath('log') 之前，通过调用新函数 app.setAppLogPath() 明确设置日志路径。＃17841
3.x.y 支持终止
🌐 End of Support for 3.x.y
根据我们的支持政策，3.x.y 已经达到生命周期终点。我们鼓励开发者和应用升级到更新版本的 Electron。
🌐 Per our support policy, 3.x.y has reached end of life. Developers and applications are encouraged to upgrade to a newer version of Electron.
应用反馈计划
🌐 App Feedback Program
我们继续使用我们的应用反馈计划进行测试。参与该计划的项目会在他们的应用上测试 Electron 测试版；作为回报，他们发现的新问题会被优先处理用于正式版本。如果你想参与或了解更多信息，请查看我们关于该计划的博客文章。
🌐 We continue to use our App Feedback Program for testing. Projects who participate in this program test Electron betas on their apps; and in return, the new bugs they find are prioritized for the stable release. If you'd like to participate or learn more, check out our blog post about the program.
下一步计划
🌐 What's Next
在短期内，你可以预期团队将继续专注于跟进构成 Electron 的主要组件的开发，包括 Chromium、Node 和 V8。虽然我们小心翼翼地避免对发布日期作出承诺，但我们的计划是大约每季度发布一次包含这些组件新版本的 Electron 主要版本。临时 7.0.0 时间表列出了 Electron 7 开发生命周期中的关键日期。此外，请参阅我们的版本控制文档以获取关于 Electron 版本控制的更详细信息。
🌐 In the short term, you can expect the team to continue to focus on keeping up with the development of the major components that make up Electron, including Chromium, Node, and V8. Although we are careful not to make promises about release dates, our plan is release new major versions of Electron with new versions of those components approximately quarterly. The tentative 7.0.0 schedule maps out key dates in the Electron 7 development life cycle. Also, see our versioning document for more detailed information about versioning in Electron.
有关即将发布的 Electron 版本中计划的重大更改的信息，请参阅我们的计划重大更改文档。
🌐 For information on planned breaking changes in upcoming versions of Electron, see our Planned Breaking Changes doc.
