fix: pin kubo interop node to unixfs-v1-2025#1083
Merged
Merged
Conversation
1 task
lidel
added a commit
to ipfs/kubo
that referenced
this pull request
Jul 8, 2026
Temporary. The published @helia/interop still expects Kubo's old CIDv0 / 256 KiB import defaults and fails against the new unixfs-v1-2025 default, so build it from the PR branch that adapts the suite (ipfs/helia#1083). Revert this commit once that PR ships to npm.
lidel
marked this pull request as draft
July 8, 2026 22:36
lidel
force-pushed
the
wip/kubo-cidv1-interop-fix
branch
from
July 8, 2026 22:58
bd3de1a to
8ae85eb
Compare
Kubo 0.43 makes unixfs-v1-2025 the default import profile (IPIP-499, https://specs.ipfs.tech/ipips/ipip-0499/), so a 10 MiB file becomes ten 1 MiB raw CIDv1 leaves instead of forty 256 KiB dag-pb leaves. The interop suite assumed the old CIDv0 / 256 KiB shape and failed against it. Pin the unixfs-v1-2025 profile on the interop Kubo node via ipfsd-ctl's init.profiles, in both the Node.js and browser fixtures, so imports are deterministic regardless of the Kubo version's default (the profile has existed since Kubo v0.40, so this also works against the 0.42 pinned here). Update the interop expectations to the v1-2025 shape: the Helia side of the unixfs-files CID comparisons, the providers root block size (now 509 bytes), and the block and dag-size assertions in unixfs-files.
lidel
force-pushed
the
wip/kubo-cidv1-interop-fix
branch
from
July 9, 2026 02:46
8ae85eb to
228b242
Compare
lidel
marked this pull request as ready for review
July 9, 2026 17:41
achingbrain
approved these changes
Jul 10, 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.
Problem
Kubo 0.42 introduced
unixfs-v1-2025(IPIP-499) and 0.43 might switch to that as the default import profile (ipfs/kubo#8185), soipfs addproduces 1 MiB chunks with raw CIDv1 leaves instead of 256 KiB dag-pb.The
providersinterop spec adds a 10 MiB file and asserts its root block is 1930 bytes, the old 40-leaf shape. Under the new default that root is 10 leaves / 509 bytes, so the interop test is outdated and fails long term.Fix
unixfs-v1-2025profile on the interop Kubo node viaipfsd-ctl'sinit.profiles, so imports are deterministic regardless of the Kubo version's default. The profile has existed since Kubo v0.40, so it also holds against the^0.42.0this package pins today.Only the interop test setup changes, no shipping Helia code. This keeps CID-based interop assertions stable across Kubo releases.