chore: bump deps for v4.0.0 release (ibc-go v10.7.0, Go 1.26.4, security fixes)#343
Merged
Conversation
tbruyelle
force-pushed
the
chore/v4-dep-security-bumps
branch
from
4f4be18 to
ab44ce1
Compare
julienrbrt
approved these changes
Jun 16, 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 join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
Dependency and security bumps to get
mainready for the v4.0.0 final release. The nightlyrun-vulncheckjob was failing with 20 reachable vulnerabilities; after these bumpsgovulncheck ./...reports 0 vulnerabilities.Changes
v0.500.0-rc3→v0.500.0(final). The final SDK addedAfterConsensusPubKeyUpdateto theStakingHooksinterface (consensus pubkey rotation); implemented as a no-op inx/coredaos/keeper/hooks.goto satisfy the interface.v10.5.0→v10.7.0— includes the v10.6.0 IBC-v2 callbacks fix and v10.7.0 transfer-v2 validation + channel/v2 query fixes. AtomOne wires transfer v2 (app/keepers/keepers.goSetRouterV2), so the transfer-v2 hardening is on a path we ship. (The v10.6.0 state-breaking change is in the callbacks/v2 middleware, which AtomOne does not wire; and v4.0.0 is already a coordinated upgrade.)1.26.1→1.26.4— clears the stdlibgovulncheckfindings (crypto/x509,net,html/template,net/textproto).UPGRADING.mdbuild instructions updated accordingly.govulncheck-reported):golang.org/x/netv0.50.0→v0.55.0,google.golang.org/grpcv1.79.1→v1.79.3,go-jose/v4v4.1.3→v4.1.4,go-viper/mapstructure/v2v2.3.0→v2.4.0.github.com/ethereum/go-ethereumv1.15.11→v1.17.0— clears the last 3 reachable findings (p2p/abi DoS).ProjectZKM/Ziren/.../zkvm_runtime), but none are linked into theatomonedbinary (go list -deps ./cmd/atomonedconfirms; they're build-tag gated in go-ethereum). If you'd prefer to keep deps aligned with ibc-go's pin, this single bump can be dropped — at the cost of 3 go-ethereum findings remaining in the nightly scan.Verification
go build ./...✅go test ./app/... ./ante/... ./post/... ./x/...✅govulncheck ./...→ No vulnerabilities found ✅🤖 Generated with Claude Code