chore(deps): update module github.com/libp2p/go-libp2p-kad-dht to v0.42.2 - #1948
Open
agntcy-automation[bot] wants to merge 1 commit into
Open
chore(deps): update module github.com/libp2p/go-libp2p-kad-dht to v0.42.2#1948agntcy-automation[bot] wants to merge 1 commit into
agntcy-automation[bot] wants to merge 1 commit into
Conversation
agntcy-automation
Bot
force-pushed
the
renovate/github.com-libp2p-go-libp2p-kad-dht-0.x
branch
from
July 31, 2026 12:45
e98494c to
bb5d098
Compare
Contributor
Author
ℹ️ Artifact update noticeFile name: cli/go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
File name: server/go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
agntcy-automation
Bot
force-pushed
the
renovate/github.com-libp2p-go-libp2p-kad-dht-0.x
branch
8 times, most recently
from
August 7, 2026 18:24
d262828 to
02b0372
Compare
agntcy-automation
Bot
force-pushed
the
renovate/github.com-libp2p-go-libp2p-kad-dht-0.x
branch
11 times, most recently
from
August 17, 2026 12:18
d1ee570 to
a72b620
Compare
agntcy-automation
Bot
force-pushed
the
renovate/github.com-libp2p-go-libp2p-kad-dht-0.x
branch
3 times, most recently
from
August 18, 2026 12:16
c2a1e17 to
8e9355b
Compare
agntcy-automation
Bot
force-pushed
the
renovate/github.com-libp2p-go-libp2p-kad-dht-0.x
branch
12 times, most recently
from
August 25, 2026 12:18
fbd5038 to
f79fbb8
Compare
agntcy-automation
Bot
force-pushed
the
renovate/github.com-libp2p-go-libp2p-kad-dht-0.x
branch
3 times, most recently
from
August 28, 2026 09:15
106b350 to
da9cec8
Compare
agntcy-automation
Bot
force-pushed
the
renovate/github.com-libp2p-go-libp2p-kad-dht-0.x
branch
2 times, most recently
from
August 31, 2026 12:36
4167340 to
044cec8
Compare
agntcy-automation
Bot
force-pushed
the
renovate/github.com-libp2p-go-libp2p-kad-dht-0.x
branch
from
September 2, 2026 12:32
044cec8 to
fd97347
Compare
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.42.2Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
libp2p/go-libp2p-kad-dht (github.com/libp2p/go-libp2p-kad-dht)
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