From the whole-branch review of #28 (#28 (comment)), finding 7: github.com/btcsuite/btcd is held at v0.25.0 while v0.26.2 is out; that release moves chaincfg into a module of its own. keyfunc imports chaincfg (internal/derive) and btcutil (hdkeychain, bech32).
Work, on a branch cut from next, PR to next: update btcd and the modules split from it to their current releases, by go get through the make targets' toolchain, keeping go.sum tidy. If the update changes any test vector, or git.eeqj.de/sneak/secret cannot build against it, do not update: say why on this issue and close it.
Definition of done
Every direct dependency is at its current release, or this issue says why btcd is held.
No test vector changes.
make check passes.
Model: opus-5-5
From the whole-branch review of https://git.eeqj.de/sneak/keyfunc/pulls/28 (https://git.eeqj.de/sneak/keyfunc/pulls/28#issuecomment-120217), finding 7: `github.com/btcsuite/btcd` is held at v0.25.0 while v0.26.2 is out; that release moves `chaincfg` into a module of its own. keyfunc imports `chaincfg` (`internal/derive`) and `btcutil` (`hdkeychain`, `bech32`).
Work, on a branch cut from `next`, PR to `next`: update `btcd` and the modules split from it to their current releases, by `go get` through the make targets' toolchain, keeping `go.sum` tidy. If the update changes any test vector, or `git.eeqj.de/sneak/secret` cannot build against it, do not update: say why on this issue and close it.
## Definition of done
- Every direct dependency is at its current release, or this issue says why `btcd` is held.
- No test vector changes.
- `make check` passes.
Model: opus-5-5
clawbot
self-assigned this 2026-10-04 06:27:15 +02:00
btcd stays at v0.25.0. From v0.26.0 on, the btcd module no longer contains the chaincfg and wire packages: they moved to new modules under new import paths (github.com/btcsuite/btcd/chaincfg/v2, github.com/btcsuite/btcd/wire/v2, and btcutil likewise to github.com/btcsuite/btcd/btcutil/v2). git.eeqj.de/sneak/secret's pkg/bip85, on both its main and next, still imports github.com/btcsuite/btcd/chaincfg and btcutil v1, which imports github.com/btcsuite/btcd/wire. With btcd at v0.26.2 nothing provides those packages, so secret cannot build, and keyfunc with it. Moving keyfunc alone to the v2 modules does not help: bip85 takes the btcutil v1 extended key type and needs the old packages itself.
v0.25.0 is the newest release that still carries those packages. Every other direct dependency is at its current release (btcutil v1.2.0 is the newest of its v1 line). The hold ends when secret moves to the v2 modules.
Closing as the brief says; nothing in the tree changes.
Model: opus-5-5
`btcd` stays at v0.25.0. From v0.26.0 on, the `btcd` module no longer contains the `chaincfg` and `wire` packages: they moved to new modules under new import paths (`github.com/btcsuite/btcd/chaincfg/v2`, `github.com/btcsuite/btcd/wire/v2`, and `btcutil` likewise to `github.com/btcsuite/btcd/btcutil/v2`). `git.eeqj.de/sneak/secret`'s `pkg/bip85`, on both its `main` and `next`, still imports `github.com/btcsuite/btcd/chaincfg` and `btcutil` v1, which imports `github.com/btcsuite/btcd/wire`. With `btcd` at v0.26.2 nothing provides those packages, so `secret` cannot build, and keyfunc with it. Moving keyfunc alone to the v2 modules does not help: `bip85` takes the `btcutil` v1 extended key type and needs the old packages itself.
v0.25.0 is the newest release that still carries those packages. Every other direct dependency is at its current release (`btcutil` v1.2.0 is the newest of its v1 line). The hold ends when `secret` moves to the v2 modules.
Closing as the brief says; nothing in the tree changes.
Model: opus-5-5
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
From the whole-branch review of #28 (#28 (comment)), finding 7:
github.com/btcsuite/btcdis held at v0.25.0 while v0.26.2 is out; that release moveschaincfginto a module of its own. keyfunc importschaincfg(internal/derive) andbtcutil(hdkeychain,bech32).Work, on a branch cut from
next, PR tonext: updatebtcdand the modules split from it to their current releases, bygo getthrough the make targets' toolchain, keepinggo.sumtidy. If the update changes any test vector, orgit.eeqj.de/sneak/secretcannot build against it, do not update: say why on this issue and close it.Definition of done
btcdis held.make checkpasses.Model: opus-5-5
btcdstays at v0.25.0. From v0.26.0 on, thebtcdmodule no longer contains thechaincfgandwirepackages: they moved to new modules under new import paths (github.com/btcsuite/btcd/chaincfg/v2,github.com/btcsuite/btcd/wire/v2, andbtcutillikewise togithub.com/btcsuite/btcd/btcutil/v2).git.eeqj.de/sneak/secret'spkg/bip85, on both itsmainandnext, still importsgithub.com/btcsuite/btcd/chaincfgandbtcutilv1, which importsgithub.com/btcsuite/btcd/wire. Withbtcdat v0.26.2 nothing provides those packages, sosecretcannot build, and keyfunc with it. Moving keyfunc alone to the v2 modules does not help:bip85takes thebtcutilv1 extended key type and needs the old packages itself.v0.25.0 is the newest release that still carries those packages. Every other direct dependency is at its current release (
btcutilv1.2.0 is the newest of its v1 line). The hold ends whensecretmoves to the v2 modules.Closing as the brief says; nothing in the tree changes.
Model: opus-5-5