build: update to Go 1.26 - #390
Conversation
vet Summary ReportThis report is generated by vet Policy Checks
Malicious Package AnalysisMalicious package analysis was performed using SafeDep Cloud API Malicious Package Analysis Report
Changed PackagesChanged Packages
Policy ViolationsPackages Violating Policy[Go]
|
|
This dependency update is currently blocked by a Go 1.26 compatibility issue in Go 1.26 made Previous Go versions parsed this value permissively, after which PMG’s This behavior remains present in goproxy v1.8.5 and its current We could temporarily set Failing CI run: https://github.com/safedep/pmg/actions/runs/29912869171 |
|
One dependency constraint to note:
|
…mage refresh (#394) * fix(deps): update golang.org/x modules to latest on the Go 1.25 line Clears the x/crypto, x/net, x/sys and x/text vulnerability findings reported against the pmg binary by image scanners. Deliberately kept back: the go directive stays 1.25.1 because the Go 1.26 move is blocked on goproxy URL parsing (see #390), and grpc stays pinned at v1.81.0 due to the trailers regression with v1.82.x. * fix(container): move runtime base to debian 13 and refresh builder pin The bullseye runtime base and the stale golang:1.25-bookworm digest (go1.25.5) accounted for most of the vulnerability findings in the published image. debian:13-slim is current stable and the refreshed golang digest carries go1.25.12, covering every flagged stdlib CVE.
Summary
Root cause
The refreshed SafeDep API dependency added internal RPCs to
MalwareAnalysisServiceClient. The hand-written analyzer test stub implemented the full generated interface explicitly, so unrelated API additions broke compilation. Embedding the generated interface keeps the stub focused on overridingQueryPackageAnalysis.Closes #201
Validation
go test ./analyzer/ -count=1go build ./...git diff --checkThe repository-wide test run was interrupted after the unrelated
packagemanagerpackage did not finish within 235 seconds; all packages reported before it passed.