Request: new stable release (6.6.3 ships a vulnerable, EOL Electron)

未关闭
  • 哪里不对？
#29,892 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
electron, go, react, react-native
领域
desktop, release

调研方向

Start by reviewing the release process and the current main commit; the issue names no release files or tests. Check which Electron version the candidate build bundles and verify the existing CI nightly or release candidate. Done means a new stable release is published with a supported Electron version.

由索引模型根据 Issue 内容生成。

描述

The current stable release (6.6.3) bundles Electron 39.2.7, which has many known vulnerabilities and is end-of-life upstream as of May 5, 2026. It’s triggering warnings from security tools, and nixpkgs has hard-deprecated the package because of it (NixOS/nixpkgs#584083).

I can see that main moved to a much newer Electron soon after 6.6.3 and has kept the version updated, but there’s been no tag since v6.6.3. I’ve been running the most recent CI nightly (6.7.0-20260917142835.2f4402a6d5) via a nixpkgs overlay and all features are working for me. Could you please cut a new stable release, perhaps from that nightly's commit, or from current main?

I'd be happy to test a release candidate if that would be useful.

Additional numbers
The number 345567
(included so the issue workflow doesn’t auto-close this)

主要语言
Go
星标
9.3k
派生
1.3k
平均合并
1 天 1 小时
30 天内合并 PR
102

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

keybase/client 的其他 Issue

查看 keybase/client 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。