Repository navigation
chore(ci): bump Go toolchain to 1.27.4 for GO-2026-6859 - #8767
Merged
Merged
Conversation
This was referenced Nov 13, 2026
Contributor
|
核对当前
以上仅为远端提交、文件及当前检查的核对;未运行本 PR 的支付改动。AI 辅助分析。 |
backend-security 的 govulncheck 现在报标准库漏洞:
Vulnerability Wei-Shaw#1: GO-2026-6859
HTTP/1 server crash due to MaxBytesReader header race in net/http
Found in: net/http@go1.27.3
Fixed in: net/http@go1.27.4
仓库把 Go 版本固定在 1.27.3(go.mod + workflow 硬断言 + 三个 Dockerfile),
所以所有 PR 的 backend-security 都会失败,与具体改动无关。
同步升级 8 处版本点:
- backend/go.mod:go 1.27.3 → 1.27.4
- security-scan.yml / backend-ci.yml(两处)/ release.yml:go1.27.4 断言
- Dockerfile / deploy/Dockerfile / backend/Dockerfile:golang:1.27.4-alpine
- DEV_GUIDE.md 的 CI 要求说明同步更新
验证:GOTOOLCHAIN=go1.27.4 go build ./... 通过,
GOTOOLCHAIN=go1.27.4 go test -tags unit ./internal/service/ 针对性用例通过。
lishuangqiang
force-pushed
the
chore/bump-go-1.27.4
branch
from
November 13, 2026 19:46
238fa3b to
a293214
Compare
Contributor
Author
大意了不好意思,已经rebase到main分支。让这个pr只专注于go的版本升级 |
Contributor
Author
|
I have read the CLA Document and I hereby sign the CLA |
This was referenced Nov 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
问题
backend-security(govulncheck)在所有 PR 上失败,报标准库漏洞:仓库把 Go 版本同时固定在多处,CI 用
go-version-file: backend/go.mod+GOTOOLCHAIN: local,所以实际编译用的就是 1.27.3;Verify Go version步骤还硬断言go version | grep -q 'go1.27.3',单独改go.mod会先在版本校验步骤失败。这不是某条 PR 引入的:
main上最后一次安全扫描成功是530c5e3a(11-11 02:43),之后的运行都是action_required;此后提交的 PR(如 #8667、#8765)在backend-security上失败的位置、漏洞编号完全一致。改动
同步升级 8 处版本点(按
DEV_GUIDE.md的升级清单):backend/go.modgo 1.27.3→go 1.27.4.github/workflows/security-scan.ymlgrep -q 'go1.27.3'→go1.27.4.github/workflows/backend-ci.yml.github/workflows/release.ymlDockerfile/deploy/DockerfileARG GOLANG_IMAGE=golang:1.27.4-alpinebackend/DockerfileFROM golang:1.27.4-alpineDEV_GUIDE.mdDEV_GUIDE.md里原本写的还是 1.27.0,与 go.mod 的 1.27.3 已经不一致,这次一并校正。验证
GOTOOLCHAIN=go1.27.4 go version→go version go1.27.4GOTOOLCHAIN=go1.27.4 go build ./...通过GOTOOLCHAIN=go1.27.4 go test -tags unit ./internal/service/(支付相关用例)通过本地无法跑
govulncheck(这台机器访问不到 proxy.golang.org,取不到golang.org/x/vuln),漏洞是否消除以本 PR 的backend-security结果为准。顺带解锁
这两条 PR 的
backend-security会在这个改动合入后重新跑并转绿。Closes #8768