Update module github.com/libp2p/go-libp2p-kad-dht to v0.42.2 - #2
Open
renovate[bot] wants to merge 1 commit into
Open
Update module github.com/libp2p/go-libp2p-kad-dht to v0.42.2#2renovate[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
3 times, most recently
from
March 23, 2026 13:14
d25cb3f to
9f97df1
Compare
renovate
Bot
force-pushed
the
renovate/github.com-libp2p-go-libp2p-kad-dht-0.x
branch
from
April 15, 2026 13:20
9f97df1 to
986e4b1
Compare
renovate
Bot
force-pushed
the
renovate/github.com-libp2p-go-libp2p-kad-dht-0.x
branch
from
April 30, 2026 02:38
986e4b1 to
9c875ca
Compare
renovate
Bot
force-pushed
the
renovate/github.com-libp2p-go-libp2p-kad-dht-0.x
branch
from
May 7, 2026 12:10
9c875ca to
ea40acb
Compare
renovate
Bot
force-pushed
the
renovate/github.com-libp2p-go-libp2p-kad-dht-0.x
branch
from
May 22, 2026 03:26
ea40acb to
aa2fbfa
Compare
renovate
Bot
force-pushed
the
renovate/github.com-libp2p-go-libp2p-kad-dht-0.x
branch
from
July 3, 2026 00:03
aa2fbfa to
881261c
Compare
renovate
Bot
force-pushed
the
renovate/github.com-libp2p-go-libp2p-kad-dht-0.x
branch
from
July 25, 2026 03:59
881261c to
1c4135c
Compare
renovate
Bot
force-pushed
the
renovate/github.com-libp2p-go-libp2p-kad-dht-0.x
branch
from
August 22, 2026 20:16
1c4135c to
6cbd05e
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.38.0→v0.42.2Release 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
v0.41.0Compare Source
What's Changed
TestBootStrapWhenRTIsEmptyby @guillaumemichel in #1264Full Changelog: libp2p/go-libp2p-kad-dht@v0.40.0...v0.41.0
v0.40.0Compare Source
Highlights
SweepingProvider.Stats()now takes acontext.Contextand returns(stats.Stats, error). Callers must pass a ctx with a deadline — the key count is fetched through the keystore worker and can stall behind a slow datastore op. (#1251 by @guillaumemichel)Fixes
ADD_PROVIDERsends so a single slow peer can't stall a reprovide cycle. (#1252 by @guillaumemichel)batchReprovidenow holdscycleStatsLkfor the full defer, fixing a stats race. (#1255 by @guillaumemichel)ResettableKeystorereset is faster and no longer blocks the worker. (#1256 by @guillaumemichel)Other
Full Changelog: libp2p/go-libp2p-kad-dht@v0.39.2...v0.40.0
v0.39.2Compare Source
What's Changed
Full Changelog: libp2p/go-libp2p-kad-dht@v0.39.1...v0.39.2
v0.39.1Compare Source
What's Changed
Full Changelog: libp2p/go-libp2p-kad-dht@v0.39.0...v0.39.1
v0.39.0Compare Source
Breaking changes
keystore.NewResettableKeystore()now takeskeystore.ResettableKeystoreOptioninstead ofkeystore.Option. Wrap existing options withKeystoreOption()to migrate.What's Changed
New Contributors
Full Changelog: libp2p/go-libp2p-kad-dht@v0.38.0...v0.39.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.