Repository navigation
fix(deps): update module github.com/libp2p/go-libp2p-kad-dht to v0.43.1 - #1059
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
Contributor
Author
ℹ️ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
renovate
Bot
force-pushed
the
renovate/github.com-libp2p-go-libp2p-kad-dht-0.x
branch
2 times, most recently
from
August 14, 2026 16:45
59f948a to
dfc8c07
Compare
renovate
Bot
force-pushed
the
renovate/github.com-libp2p-go-libp2p-kad-dht-0.x
branch
from
August 21, 2026 09:33
dfc8c07 to
00cdea7
Compare
renovate
Bot
force-pushed
the
renovate/github.com-libp2p-go-libp2p-kad-dht-0.x
branch
from
September 3, 2026 06:57
00cdea7 to
9591081
Compare
renovate
Bot
force-pushed
the
renovate/github.com-libp2p-go-libp2p-kad-dht-0.x
branch
from
October 28, 2026 17:45
9591081 to
5ce6d04
Compare
renovate
Bot
force-pushed
the
renovate/github.com-libp2p-go-libp2p-kad-dht-0.x
branch
2 times, most recently
from
November 16, 2026 07:22
2912f84 to
4c8c7ac
Compare
renovate
Bot
force-pushed
the
renovate/github.com-libp2p-go-libp2p-kad-dht-0.x
branch
from
November 19, 2026 07:43
4c8c7ac to
8bf029b
Compare
renovate
Bot
force-pushed
the
renovate/github.com-libp2p-go-libp2p-kad-dht-0.x
branch
from
November 21, 2026 14:01
8bf029b to
4cfb63c
Compare
This branch has not been deployed
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
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.
This PR contains the following updates:
v0.41.0→v0.43.1Release Notes
libp2p/go-libp2p-kad-dht (github.com/libp2p/go-libp2p-kad-dht)
v0.43.1Compare Source
Changed
go-libp2pv0.52.0 (from v0.50.0), which bringsquic-gov0.64.1 and releases connections that close before they are accepted. The exported API is unchanged, and Go 1.26 remains the minimum version. #1311Fixed
GetValueandSearchValuewith a quorum no longer leave their lookup running once the quorum is reached. Queries still in flight stayed blocked until the caller's context ended, and kept the lookup's goroutines alive with them; with a context that has no deadline, they never exited. #1309ProvidewithEnableOptimisticProvidenow returns when the lookup finds no peer to sendADD_PROVIDERto, for example because every routing table peer is unreachable. It used to block forever, whatever its context. #1309rtrefresh: a refresh that stops at a common prefix length with no peers now signals completion, so the DHT leaves its bootstrap phase. #1310v0.43.0Compare Source
Highlights
Routing table persists across restarts (#1299)
The DHT now saves its routing table peers, with their addresses, to its
Datastore, and dials them the next time its routing table is empty. A restarting node no longer depends only on the bootstrap peers to rejoin the network: a node joining the Amino DHT reached 100 routing table peers in about 2s instead of 11–22s, with fewer file descriptors and connections.RoutingTablePersistence(interval)sets how often the snapshot is saved (hourly by default, and once more onClose).RoutingTablePersistence(0)turns persistence off.BootstrapOrderpicks what the DHT dials first when its routing table is empty:BootstrapFirst(default, saved peers as a fallback),PersistedFirst, orConcurrent.dualturns persistence off for the LAN DHT.fullrtis unchanged.Behavior changes: persistence is on by default and writes one key,
/kad-dht/routing-table/<protocol ID>, to theDatastorethe DHT is given. A DHT with no bootstrap peers but a datastore that survives restarts now dials its saved peers after a restart, where it used to dial nothing. UseRoutingTablePersistence(0)to keep the old behavior.What's Changed
Full Changelog: libp2p/go-libp2p-kad-dht@v0.42.2...v0.43.0
v0.42.2Compare Source
Highlights
Provider record writes are batched again (#1293)
v0.42.0 (#1277) inadvertently turned every provider record write and GC delete into an individual (fsynced) datastore operation, causing excessive disk I/O on busy nodes (ipfs/kubo#11432). Provider writes and GC deletes are now batched (256 records per batch), restoring the pre-v0.42.0 fsync rate. No protocol or record-layout change.
Local provider record writes respect shutdown (#1288)
The
WithAddLocalRecordcallback now receives the sweeping provider's lifecycle context instead ofcontext.Background()(a regression from #1282), so local provider record writes are properly cancelled when the provider shuts down.What's Changed
Full Changelog: libp2p/go-libp2p-kad-dht@v0.42.1...v0.42.2
v0.42.1Compare Source
What's Changed
Full Changelog: libp2p/go-libp2p-kad-dht@v0.42.0...v0.42.1
v0.42.0Compare Source
Highlights
Constructors no longer take a
context.Context(#1282)The lifecycle context was removed from all constructors. The DHT now runs until
Close()is called; cancelling a context no longer tears it down.dht.New(ctx, h, opts...)dht.New(h, opts...)dht.NewDHT(ctx, h, dstore)dht.NewDHT(h, dstore)dht.NewDHTClient(ctx, h, dstore)dht.NewDHTClient(h, dstore)dual.New(ctx, h, opts...)dual.New(h, opts...)records.NewProviderManager(ctx, ...)records.NewProviderManager(...)rtrefresh.NewRtRefreshManager(ctx, ...)rtrefresh.NewRtRefreshManager(...)Migration: drop the context argument. If you relied on cancelling the constructor context to shut the DHT down, call
Close()instead.Close()blocks until all long-lived components have stopped. Note that in-flight RPC handlers are owned by the libp2p host, so close the host before closing any datastore handed to the DHT.ProviderStoreoption removed (#1277 by @guillaumemichel)Custom
ProviderStoreimplementations can no longer be injected; the DHT always runs the built-in provider manager. Thedht.ProviderStore(...)option is replaced by datastore-level configuration:New options:
ValueDatastoreandProviderDatastoregive value and provider records their own physical datastores (both default to the datastore set withDatastore). Thedht.ProviderStore()getter onIpfsDHTremains available.Value records are stored under namespaced datastore keys (#1277)
Value records used to be stored at the datastore root as
/<base32(key)>; they are now namespaced by record type:/<namespace>/<base32(key)>(e.g./pk/...,/ipns/...). This keeps a shared datastore collision-free and enables per-namespace garbage collection.Migration: there is no automatic key migration. On upgrade, value records persisted by earlier versions are simply not found under the new layout — nodes will re-store them as the network republishes (records expire after
MaxRecordAge, 48h by default, anyway). If you persist the DHT datastore and want to reclaim space, you can delete leftover root-level base32 keys. Provider records are unaffected (already namespaced under/providers/).What's Changed
Full Changelog: libp2p/go-libp2p-kad-dht@v0.41.0...v0.42.0
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.