Skip to content

chore: update Go dependencies for 1.17 post-release#290

Open
nelson-parente wants to merge 1 commit intomasterfrom
post-release/1.17-dependency-cleanup
Open

chore: update Go dependencies for 1.17 post-release#290
nelson-parente wants to merge 1 commit intomasterfrom
post-release/1.17-dependency-cleanup

Conversation

@nelson-parente
Copy link
Copy Markdown

Summary

Part of v1.17 post-release checklist (dapr/dapr#9281). Also see PR #287 for panic fix.

This PR updates indirect Go dependencies to their latest compatible versions under the current Go 1.25.1 toolchain:

  • golang.org/x/crypto: v0.46.0 → v0.49.0 (security)
  • golang.org/x/net: v0.48.0 → v0.52.0 (security)
  • golang.org/x/sys: v0.39.0 → v0.42.0
  • golang.org/x/text: v0.32.0 → v0.35.0
  • golang.org/x/oauth2: v0.34.0 → v0.36.0
  • golang.org/x/sync: v0.19.0 → v0.20.0
  • golang.org/x/mod: v0.31.0 → v0.33.0
  • golang.org/x/term: v0.38.0 → v0.41.0
  • golang.org/x/tools: v0.40.0 → v0.42.0
  • google.golang.org/grpc: v1.78.0 → v1.79.3
  • github.com/prometheus/procfs: v0.19.2 → v0.20.1

Known Blockers

go get -u ./... (full upgrade) could not be run because:

  • github.com/dapr/dapr v1.17.3 requires go >= 1.25.8 (current toolchain: go 1.25.1)
  • github.com/dapr/durabletask-go v0.11.3 requires go >= 1.26.0

Direct dependencies (dapr/dapr, dapr/components-contrib, dapr/cli) remain pinned at v1.16.5. A follow-up PR should upgrade the Go toolchain and then re-run the full dependency update.

Frontend (web/)

The Angular frontend (web/package.json) is on Angular 12; latest is Angular 21. This is a major version upgrade that requires a separate effort and is out of scope for this post-release cleanup.

GitHub Dependabot reports 49 vulnerabilities (4 critical, 17 high) on the default branch — many likely originate from the pinned Angular 12 frontend and the locked Go direct deps.

Test plan

  • Verify CI passes (build + tests)
  • Confirm no breaking changes from golang.org/x/* updates
  • Review Dependabot alerts to confirm which are addressed by this PR
  • Follow-up: upgrade Go toolchain to >= 1.25.8 and re-run full dep update
  • Follow-up: evaluate Angular upgrade path (12 -> 21)

@JoshVanL
Copy link
Copy Markdown

JoshVanL commented Apr 1, 2026

@nelson-parente see DCO

Update golang.org/x/* and other indirect dependencies to latest
compatible versions with the current Go 1.25.1 toolchain:

- golang.org/x/crypto: v0.46.0 -> v0.49.0
- golang.org/x/net: v0.48.0 -> v0.52.0
- golang.org/x/sys: v0.39.0 -> v0.42.0
- golang.org/x/text: v0.32.0 -> v0.35.0
- golang.org/x/oauth2: v0.34.0 -> v0.36.0
- golang.org/x/sync: v0.19.0 -> v0.20.0
- golang.org/x/mod: v0.31.0 -> v0.33.0
- golang.org/x/term: v0.38.0 -> v0.41.0
- golang.org/x/tools: v0.40.0 -> v0.42.0
- google.golang.org/grpc: v1.78.0 -> v1.79.3
- github.com/prometheus/procfs: v0.19.2 -> v0.20.1

Run go mod tidy to prune unused entries.

Note: go get -u ./... (full upgrade) was blocked because
github.com/dapr/dapr v1.17.3 requires go >= 1.25.8 and
github.com/dapr/durabletask-go v0.11.3 requires go >= 1.26.0,
but the current toolchain is go 1.25.1. The core dapr/dapr and
dapr/components-contrib direct deps remain pinned at v1.16.5 until
the toolchain is updated.

Signed-off-by: Nelson Parente <nelson_parente@live.com.pt>
@nelson-parente nelson-parente force-pushed the post-release/1.17-dependency-cleanup branch from 107109e to 0d797e9 Compare April 1, 2026 13:58
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.

2 participants