Skip to content

build(deps): bump golang.org/x/net from 0.57.0 to 0.58.0 in the golang-x group - #4245

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/go_modules/golang-x-656397456c
Open

build(deps): bump golang.org/x/net from 0.57.0 to 0.58.0 in the golang-x group#4245
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/go_modules/golang-x-656397456c

build(deps): bump golang.org/x/net in the golang-x group

ee65b4c
Select commit
Loading
Failed to load commit list.
buildsworth-bk-app / Buildsworth review succeeded Aug 17, 2026 in 9m 40s

Review submitted — approved

Review summary: buildkite/agent PR #4245

Change reviewed

This PR updates the direct production dependency golang.org/x/net from v0.57.0 to v0.58.0. The new module requirements also move the indirect dependencies golang.org/x/crypto to v0.55.0, golang.org/x/text to v0.41.0, and golang.org/x/tools to v0.48.0; go.sum is updated for the same four modules. No application source files are changed.

The agent directly imports golang.org/x/net/http2 in internal/agenthttp/client.go, where http2.ConfigureTransports configures the shared HTTP transport used by the API and several artifact clients. I traced the package usage with go mod why and go list -deps: the production build also reaches x/net/idna, selected x/crypto packages such as PKCS#12 and ChaCha20-Poly1305, and Unicode packages from x/text. The x/tools update is reached through the repository's assertzapper tool rather than an agent runtime path.

Evidence inspected

  • Read the complete GitHub diff and both changed files, go.mod and go.sum.
  • Compared the upstream golang/net v0.57.0...v0.58.0 range. It contains 14 commits, including fixes in HTTP/2 connection state callbacks and HPACK table initialization, plus HTTP/3, QUIC, DNS, and proxy-environment changes. Of those areas, this repository directly imports HTTP/2; the changed httpproxy package is not imported by the agent.
  • Read the upstream module requirements for both x/net versions. v0.58.0 still requires Go 1.25 and accounts for the x/crypto and x/text updates in this PR. The updated x/text module in turn accounts for x/tools v0.48.0.
  • Inspected the corresponding upstream x/crypto, x/text, and x/tools version ranges and the relevant package usage in this repository. I found no incompatible API change in a package used by the agent.
  • Confirmed all four new go.sum entries against sum.golang.org.
  • Checked the PR conversation and review threads. There were no prior inline review comments or prior buildsworth reviews, and no Linear issue was linked. The branch-name fragment that superficially matched the issue-ID pattern did not resolve to a Linear issue.
  • Socket Security's project and pull-request checks were successful. The main buildkite/agent Buildkite build was still pending at the last status check; the supplied Buildkite API credentials could not directly read that organization/build, so its job-level status was not independently available during the review.

No separate automated code-review tool was exposed in this session, so the diff and affected dependency paths were reviewed manually.

Checks run

Using Go 1.26.5, matching this branch's go.mod:

  • go mod verify passed.
  • go mod tidy completed without changing go.mod or go.sum.
  • go test ./internal/agenthttp ./api/... passed (internal/agenthttp has no test files, and the API tests passed).
  • go test golang.org/x/net/http2 passed.
  • Focused tests for the selected x/net, x/crypto, and x/text packages in the agent's dependency graph passed, including HTTP/2 HPACK, IDNA, PKCS#12, ChaCha20-Poly1305, Unicode normalization, and bidirectional-text handling.
  • A full go test ./... was attempted. The first attempt encountered the checkout's documented container-only SSH alias setup failure. After installing .buildkite/build/ssh.conf in the documented system location, internal/job passed, but the full run could not complete because the Go compiler was killed while compiling the very large AWS EC2 SDK package. Retrying sequentially with go test -p 1 ./... hit the same resource limit. The failure was environmental and not in a package changed by this dependency update, but the complete local suite was therefore not verified.

Findings and verdict

I found no actionable correctness, compatibility, security, or manifest-consistency issue. The changed versions and checksums are internally consistent, the directly affected HTTP/2 package and relevant transitive packages passed focused tests, and the upstream delta does not expose a breaking change at the agent's call site.

The submitted GitHub review was APPROVE with no inline comments: #4245 (review)

Trigger source: automatic.