sops updates: panic: interface conversion: interface {} is float64, not string

[mrdev023]

Step to reproduce

• Add pgp key and crypt file with it
• Add age key
• Run sops updatekeys <file>

Logs

panic: interface conversion: interface {} is float64, not string

goroutine 1 [running]:
github.com/getsops/sops/v3/stores/dotenv.(*Store).EmitPlainFile(0xc00034c350?, {0xc000011e18?, 0xc00034c236?, 0xc00034c236?})
	github.com/getsops/sops/v3/stores/dotenv/store.go:144 +0x2a9
github.com/getsops/sops/v3/stores/dotenv.(*Store).EmitEncryptedFile(_, {{{0x0, 0xee043e95b, 0x0}, {0xc00078a790, 0xc}, {0x0, 0x0}, {0x0, 0x0}, ...}, ...})
	github.com/getsops/sops/v3/stores/dotenv/store.go:129 +0x40e
github.com/getsops/sops/v3/cmd/sops/subcommand/updatekeys.updateFile({{0xc0001c56c0, 0x35}, 0x0, {0xc0004531f0, 0x1, 0x1}, {0x0, 0x0, 0x0}, 0x1, ...})
	github.com/getsops/sops/v3/cmd/sops/subcommand/updatekeys/updatekeys.go:111 +0x847
github.com/getsops/sops/v3/cmd/sops/subcommand/updatekeys.UpdateKeys({{0xc0001c56c0, 0x35}, 0x0, {0xc0004531f0, 0x1, 0x1}, {0x0, 0x0, 0x0}, 0x1, ...})
	github.com/getsops/sops/v3/cmd/sops/subcommand/updatekeys/updatekeys.go:40 +0xb8
main.main.func8(0xc000227080)
	github.com/getsops/sops/v3/cmd/sops/main.go:704 +0x2b8
github.com/urfave/cli.HandleAction({0x18be920?, 0x1d56ac8?}, 0xa?)
	github.com/urfave/cli@v1.22.16/app.go:524 +0x70
github.com/urfave/cli.Command.Run({{0x1cd3d6d, 0xa}, {0x0, 0x0}, {0x0, 0x0, 0x0}, {0x1d263a4, 0x33}, {0x0, ...}, ...}, ...)
	github.com/urfave/cli@v1.22.16/command.go:175 +0x676
github.com/urfave/cli.(*App).Run(0xc000682540, {0xc000050050, 0x5, 0x5})
	github.com/urfave/cli@v1.22.16/app.go:277 +0xb1b
main.main()
	github.com/getsops/sops/v3/cmd/sops/main.go:1989 +0x6e55

Other informations

.sops.yaml

creation_rules:
  - path_regex: secrets/[^/]+\.(yaml|json|env|ini|txt)$
    key_groups:
      - pgp:
        - <my pgp fingerprint>
      - age:
        - <my new age public key>

Sops version: 3.10.2

[felixfontein]

This is an issue with Shamir threshold and DotEnv files; it has already been fixed in #1899, but the fix hasn't been included in a new release yet.

[mrdev023]

Okay, I can juste patch the current release with the patch? Or it depend of upstream works?