Felix Fontein

Restart CI.

My guess that this is related with updates to goreleaser, so I would suggest to add a test which runs regularly (maybe weekly, just to make sure it still works)...

The behavior changed in nFPM 2.33.1 (https://github.com/goreleaser/nfpm/releases/tag/v2.33.1; more precisely: https://github.com/goreleaser/nfpm/pull/715), which was included in goreleaser 1.21.0 (https://github.com/goreleaser/goreleaser/releases/tag/v1.21.0), which we switched to in https://github.com/getsops/sops/pull/1427/files#diff-87db21a973eed4fef5f32b267aa60fcee5cbdf03c67fafdc2a9b553bb0b15f34R68 - the PR assumed that `version: 1.20.x`...

There's another YAML library for Golang: https://github.com/goccy/go-yaml It seems to be actively maintained. Maybe we should consider migrating to that one? There seems to be no other actively maintained YAML...

I did some first experiments. Simply unmarshaling data is very simple, for example the only change needed for `config/config.go` to use that library is ```diff --- a/config/config.go +++ b/config/config.go @@...

Update: I now know how to distinguish between strings and other formats; see https://github.com/goccy/go-yaml/issues/661#issuecomment-2661410461. I've updated https://gist.github.com/felixfontein/f53e704961c3b241810e061083017a5e to print more infos.

With goccy/go-yaml, we could also round-trip the *representation* of values, like encrypt and decrypt `0x1_5` instead of converting it to `21` (like now). Something similar could also be done for...

- go-yaml.v3 is now officially deprecated: https://github.com/go-yaml/yaml/commit/944c86a7d29391925ed6ac33bee98a0516f1287a - there's a new maintained fork of it: https://github.com/yaml/go-yaml/ - and we have a PR that switches usage to it: #1934 :tada: I...