Updates every direct dependency to its current release and runs go mod tidy.
Bumped: filippo.io/age v1.2.1 to v1.3.2, spf13/cobra v1.9.1 to
v1.10.2, stretchr/testify v1.8.4 to v1.12.1, golang.org/x/crypto
v0.38.0 to v0.57.0 (the ssh/agent fixes the issue names), golang.org/x/term
v0.32.0 to v0.46.0, btcsuite/btcd/btcutil v1.1.6 to v1.2.0, and btcsuite/btcd v0.24.2 to v0.25.0. tyler-smith/go-bip39 is already at
its latest (v1.1.0) and git.eeqj.de/sneak/secret at its latest commit.
Only go.mod and go.sum change; no source edits were needed and no
test vector moved. make check is green.
What a reader would trip over: btcd is held at v0.25.0, one release
short of current. v0.26.x moved the chaincfg and wire packages into
separate /v2 modules. keyfunc imports the v1 chaincfg path, and our
pinned secret dependency (via bip85) pulls v1 btcutil, which imports
the v1 wire path; both vanish in v0.26.x. v0.25.0 is the newest release
that still ships those v1 packages. Taking v0.26.x is a breaking
migration that also needs upstream secret work, so it is out of scope
for this issue.
Held back, one line each:
btcsuite/btcd: v0.26.x removes the v1 chaincfg/wire packages we
and secret depend on; see above.
Judgement call: go mod tidy normalized the go directive from 1.26
to 1.26.0; left as tidy produced it.
Disclosure: the standardized .golangci.yml emits a gomodguard
deprecation warning under golangci-lint v2.12.2 (linter renamed to gomodguard_v2); lint still reports 0 issues. Not fixed here because
that file is vendored and changes only via the prompts repo; worth a
follow-up issue there.
Updates every direct dependency to its current release and runs `go mod tidy`.
Bumped: `filippo.io/age` v1.2.1 to v1.3.2, `spf13/cobra` v1.9.1 to
v1.10.2, `stretchr/testify` v1.8.4 to v1.12.1, `golang.org/x/crypto`
v0.38.0 to v0.57.0 (the ssh/agent fixes the issue names), `golang.org/x/term`
v0.32.0 to v0.46.0, `btcsuite/btcd/btcutil` v1.1.6 to v1.2.0, and
`btcsuite/btcd` v0.24.2 to v0.25.0. `tyler-smith/go-bip39` is already at
its latest (v1.1.0) and `git.eeqj.de/sneak/secret` at its latest commit.
Only `go.mod` and `go.sum` change; no source edits were needed and no
test vector moved. `make check` is green.
What a reader would trip over: `btcd` is held at v0.25.0, one release
short of current. v0.26.x moved the `chaincfg` and `wire` packages into
separate `/v2` modules. keyfunc imports the v1 `chaincfg` path, and our
pinned `secret` dependency (via bip85) pulls v1 `btcutil`, which imports
the v1 `wire` path; both vanish in v0.26.x. v0.25.0 is the newest release
that still ships those v1 packages. Taking v0.26.x is a breaking
migration that also needs upstream `secret` work, so it is out of scope
for this issue.
Held back, one line each:
- `btcsuite/btcd`: v0.26.x removes the v1 `chaincfg`/`wire` packages we
and `secret` depend on; see above.
Judgement call: `go mod tidy` normalized the `go` directive from `1.26`
to `1.26.0`; left as tidy produced it.
Disclosure: the standardized `.golangci.yml` emits a `gomodguard`
deprecation warning under golangci-lint v2.12.2 (linter renamed to
`gomodguard_v2`); lint still reports 0 issues. Not fixed here because
that file is vendored and changes only via the `prompts` repo; worth a
follow-up issue there.
Issue: https://git.eeqj.de/sneak/keyfunc/issues/19
Model: opus-4-8
Direct deps bumped to their latest release: age v1.2.1 to v1.3.2,
cobra v1.9.1 to v1.10.2, testify v1.8.4 to v1.12.1, x/crypto v0.38.0
to v0.57.0, x/term v0.32.0 to v0.46.0, btcutil v1.1.6 to v1.2.0,
btcd v0.24.2 to v0.25.0. go-bip39 is already at v1.1.0 and the secret
module at its latest commit.
btcd is held at v0.25.0: v0.26.x moved the chaincfg and wire packages
into separate /v2 modules, a breaking migration our chaincfg import and
the pinned secret dependency's v1 btcutil cannot take without upstream
work. go mod tidy normalized the go directive to 1.26.0. No test vector
changed.
Model: opus-4-8
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.
Updates every direct dependency to its current release and runs
go mod tidy.Bumped:
filippo.io/agev1.2.1 to v1.3.2,spf13/cobrav1.9.1 tov1.10.2,
stretchr/testifyv1.8.4 to v1.12.1,golang.org/x/cryptov0.38.0 to v0.57.0 (the ssh/agent fixes the issue names),
golang.org/x/termv0.32.0 to v0.46.0,
btcsuite/btcd/btcutilv1.1.6 to v1.2.0, andbtcsuite/btcdv0.24.2 to v0.25.0.tyler-smith/go-bip39is already atits latest (v1.1.0) and
git.eeqj.de/sneak/secretat its latest commit.Only
go.modandgo.sumchange; no source edits were needed and notest vector moved.
make checkis green.What a reader would trip over:
btcdis held at v0.25.0, one releaseshort of current. v0.26.x moved the
chaincfgandwirepackages intoseparate
/v2modules. keyfunc imports the v1chaincfgpath, and ourpinned
secretdependency (via bip85) pulls v1btcutil, which importsthe v1
wirepath; both vanish in v0.26.x. v0.25.0 is the newest releasethat still ships those v1 packages. Taking v0.26.x is a breaking
migration that also needs upstream
secretwork, so it is out of scopefor this issue.
Held back, one line each:
btcsuite/btcd: v0.26.x removes the v1chaincfg/wirepackages weand
secretdepend on; see above.Judgement call:
go mod tidynormalized thegodirective from1.26to
1.26.0; left as tidy produced it.Disclosure: the standardized
.golangci.ymlemits agomodguarddeprecation warning under golangci-lint v2.12.2 (linter renamed to
gomodguard_v2); lint still reports 0 issues. Not fixed here becausethat file is vendored and changes only via the
promptsrepo; worth afollow-up issue there.
Issue: #19
Model: opus-4-8
Review passed.
Model: opus-4-8