Skip to content

Bump golang.org/x/crypto and go-chi/chi to close Dependabot alerts - #24

Merged
jdtw merged 1 commit into
mainfrom
chore/bump-vulnerable-deps
Jul 31, 2026
Merged

jdtw merged 1 commit into
mainfrom
chore/bump-vulnerable-deps

Conversation

@jdtw

@jdtw jdtw commented Jul 31, 2026

Copy link
Copy Markdown
Owner

Summary

  • Bump golang.org/x/crypto v0.46.0 → v0.54.0, resolving 13 open Dependabot alerts (7 critical, 2 high, 4 medium). All in the SCRAM auth path pulled in transitively via pgconn; nothing in this repo imports it directly.
  • Bump go-chi/chi/v5 v5.2.3 → v5.3.1, resolving an open-redirect alert in RedirectSlashes — a middleware this app doesn't actually use.
  • x/crypto v0.54.0 requires Go 1.25, so go mod tidy also bumped the go.mod go directive from 1.24.0 → 1.25.0. Already satisfied by CI (actions/setup-go with go-version: 1.25.x) and the Dockerfile (golang:1.25-alpine), so no other changes were needed.

Remaining 2 alerts (pgproto3/v2, pgx/v4) have no fix available in the pgx v4 line — only pgx v5.9.2+ — and are left for a separate pgx v4→v5 migration.

Test plan

  • go build ./...
  • go vet ./...
  • go test ./...
  • ./docker_test.sh — full integration suite against a real Postgres instance, exercising the actual pgconn/x/crypto connection path

🤖 Generated with Claude Code

x/crypto v0.46.0 -> v0.54.0 resolves 13 open alerts (7 critical, 2
high, 4 medium), all in the SCRAM auth path pulled in transitively via
pgconn; none of it is imported directly. go-chi/chi v5.2.3 -> v5.3.1
resolves an open-redirect alert in RedirectSlashes, a middleware this
app doesn't use.

x/crypto v0.54.0 requires go 1.25, so `go mod tidy` also bumped the
go.mod go directive from 1.24.0 to 1.25.0 -- already satisfied by both
CI (actions/setup-go with go-version: 1.25.x) and the Dockerfile
(golang:1.25-alpine), so no other changes needed.

Verified with the full docker-based integration suite (./docker_test.sh)
against a real Postgres instance, exercising the actual pgconn/x-crypto
connection path.

The remaining two alerts (pgproto3/v2, pgx/v4) have no fix in the pgx
v4 line -- only pgx v5.9.2+ -- and are left for a separate pgx v4->v5
migration.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@jdtw
jdtw merged commit 454c6e2 into main Jul 31, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant