fix(deps): update module github.com/quic-go/quic-go to v0.62.0 - #2996
fix(deps): update module github.com/quic-go/quic-go to v0.62.0#2996renovate[bot] wants to merge 1 commit into
Conversation
ℹ️ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
pikachuren
left a comment
There was a problem hiding this comment.
🙏 感谢 @app/renovate 提交!
🤖 AI 自动审核声明:本评审报告由 AI 自动生成,当前使用 Claude Opus 5 模型进行分析。
🎯 结论
🔄 Request Changes — 上游代码本身安全,但本 PR 同时把 go 1.25.0 提升到 go 1.26.0,需要维护者确认是否接受
📖 概要
fix(deps): update module github.com/quic-go/quic-go to v0.62.0 · Renovate 自动依赖升级。
核心改动:quic-go v0.61.0 → v0.62.0,同时将 go.mod 的 go directive 从 1.25.0 提升到 1.26.0。
🧭 整体方案
版本号提升,无业务代码改动。但 quic-go v0.62.0 要求更高的 Go 版本,Renovate 因此连带修改了 go directive——这一点会影响整个项目的最低 Go 版本要求和 CI 镜像,属于超出「依赖升级」范畴的隐性影响,值得单独确认。
📊 变更统计
2 个文件(+4 / -2 行) | 功能 ⭐⭐⭐⭐ | 最小改动 ⭐⭐⭐ | 前向兼容 ⭐⭐⭐ | 方案设计 ⭐⭐⭐⭐
🚨 关键问题
P0(阻塞合并):无
P1(建议修复):
⚠️ go.mod—go 1.25.0→go 1.26.0会抬高整个项目的最低 Go 版本门槛,影响 CI 构建镜像、发行版打包以及下游二次开发者的工具链要求。请问项目当前是否已准备好全面切换到 Go 1.26?如果 CI 里还有固定 1.25 的 job,合并后可能直接构建失败。是否考虑先确认 CI 配置同步、或等 Go 1.26 更稳定后再合入呢?
P2(可选):
- 💡 建议在 PR 描述中显式标注「本次升级附带 Go 版本要求提升」,避免维护者仅按普通依赖升级处理而忽略这一点~
🔐 依赖安全审查
- 审查范围:
quic-gov0.61.0 → v0.62.0,上游 44 个 commits、120 个文件(+3078/-1201) - 审查方式:拉取
quic-go/quic-go仓库 v0.61.0...v0.62.0 完整 diff,并对生产代码做恶意模式扫描 - 安全评估:✅ 无恶意代码
- 详细结论:
- 未发现
exec.Command/os/exec/ 异常http.Post/net.Dial回连 / base64 混淆负载 /unsafe.Pointer滥用 - 改动主要为协议实现优化、CI workflow 调整(clusterfuzz、govulncheck、cross-compile 等)与测试补充
go.mod新增项仅github.com/stretchr/testify v1.12.1(测试依赖)与go.yaml.in/yaml/v3 v3.0.5(indirect),无可疑第三方包- 上游为知名活跃项目,有 fuzzing 与 govulncheck 常态化流程
- 未发现
✅ 待处理清单
- [P1] 确认项目是否接受最低 Go 版本提升到 1.26,并同步检查 CI / Dockerfile / 打包脚本中的 Go 版本
- [P2] 在 PR 描述中标注 Go 版本要求变更
🎯 结论:🔄 Request Changes — 上游代码安全无虞,但 Go 版本门槛提升需维护者明确确认后再合并。
This PR contains the following updates:
v0.61.0→v0.62.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
quic-go/quic-go (github.com/quic-go/quic-go)
v0.62.0Compare Source
This release adds support for stream priorities based on RFC 9218:
SendStreamandStreamnow exposeSetPriority, allowing applications to set the urgency and incremental scheduling behavior of stream data. Retransmissions are prioritized over new stream data and respect stream priorities: #5770, #5774Priorityheaders andPRIORITY_UPDATEframes. Priority updates are also recorded in qlog for both HTTP/3 and QUIC streams: #5783, #5789, #5790, #5795Notable Changes
http3.Streamandhttp3.RequestStreamnow exposeTryWriteAll, which queues a complete DATA frame without blocking or returnsquic.ErrWouldBlockwithout queueing anything: #5765Breaking Changes
Notable Fixes
:authorityare now rejected for HTTP and HTTPS URIs: #5825Hostis now used for HTTP and HTTPS requests when:authorityis omitted, while conflictingHostand:authorityvalues are rejected: #5828:schemeare now rejected: #5829Hostheader fields are now rejected: #5830Content-Encodingheader: #5834Conn.NextConnectionnow returns the connection context's error if the connection closes before the handshake completes: #5764, thanks to @floating-catChangelog
New Contributors
Full Changelog: quic-go/quic-go@v0.61.0...v0.62.0
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.