next → main: v1.0.0-rc2 #82

Open
clawbot wants to merge 2 commits from next into main
Collaborator

next at v1.0.0-rc2 adds one change over main:

  • --index/-n and --words take decimal digits only. -n 010 is index 10 (it was read as octal and derived key 8), and 0x10, 1_0 or a sign is refused, naming the flag. #75, #81.

next also has its own commit for #70, which main already carries as #72; the two are the same change and merge cleanly.

The audit of v1.0.0-rc1 left six minor findings open, none of them on this branch: #74, #76, #77, #78, #79, #80.

Model: opus-5-5

`next` at `v1.0.0-rc2` adds one change over `main`: - `--index`/`-n` and `--words` take decimal digits only. `-n 010` is index 10 (it was read as octal and derived key 8), and `0x10`, `1_0` or a sign is refused, naming the flag. https://git.eeqj.de/sneak/keyfunc/issues/75, https://git.eeqj.de/sneak/keyfunc/pulls/81. `next` also has its own commit for https://git.eeqj.de/sneak/keyfunc/issues/70, which `main` already carries as https://git.eeqj.de/sneak/keyfunc/pulls/72; the two are the same change and merge cleanly. The audit of `v1.0.0-rc1` left six minor findings open, none of them on this branch: https://git.eeqj.de/sneak/keyfunc/issues/74, https://git.eeqj.de/sneak/keyfunc/issues/76, https://git.eeqj.de/sneak/keyfunc/issues/77, https://git.eeqj.de/sneak/keyfunc/issues/78, https://git.eeqj.de/sneak/keyfunc/issues/79, https://git.eeqj.de/sneak/keyfunc/issues/80. Model: opus-5-5
clawbot added 2 commits 2026-10-13 02:38:06 +02:00
sneak/secret now carries its own copy of go-bip39
(sneak/secret#130), so requiring it at that
commit, ef0ae90, lets go mod tidy drop go-bip39 from go.sum. Earlier,
secret renamed its module to sneak.berlin/go/secret
(sneak/secret#43), so the requirement, the
two imports of its bip85 package and the README sentence naming that
package move to the new path. The bip85 functions keyfunc calls are
unchanged, and no other requirement moves.

Model: opus-5-5
Co-authored-by: clawbot <sneak+clawbot@sneak.cloud>
Both flags were uint32 flags, which the flag library reads with base-0 rules, so `-n 010` derived key 8 and `0x10` or `1_0` were accepted. Both now hold options.Decimal, a flag value whose Set parses with strconv.ParseUint(text, 10, 32): a leading zero stays decimal, and a base prefix, an underscore, a sign or an empty value is refused with an error naming the flag while the flags are parsed, before any command runs. Its type is still named uint32, so --help is unchanged and GetUint32 still reads it back. The README says the index is a decimal number.

Model: opus-5-5
clawbot added the merge-ready label 2026-10-13 02:38:07 +02:00
sneak was assigned by clawbot 2026-10-13 02:38:08 +02:00
Some checks are pending
check / check (push) Waiting to run
You are not authorized to merge this pull request.
This pull request can be merged automatically.
This branch is out-of-date with the base branch
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin next:next
git checkout next
Sign in to join this conversation.