Release fxamacker/cbor v2.6.0

[fxamacker]

Tagging v2.6.0 looks worthwhile, so new PRs opened after January 12, 2024 may need to wait for next release. For context, it takes time to test and fuzz new features and new releases.

Notable new features and optimizations already merged include:

• Add FieldNameMatching decode option. #433
• Add encoding option to specify how omitempty fields are encoded #453
• Add option to decode CBOR bignum to interface{} as *big.Int #456
• Add 2 more options for decoding CBOR integers to interface{} #457
• New options for encoding Go strings to and from CBOR byte strings #465

Other changes include bug fixes and refactored unit tests.

Some new settings are better, faster, or use less memory (sometimes all three), so they should be used whenever feasible.

💡 Users can control trade-offs and get better results by using non-default settings. CBOR encoders can encode data with different CBOR options and generic CBOR decoders will still be able to decode the data. This is kind of like gzip being able to uncompress files even when different compression level was used.

[fxamacker]

PR #464 passed 100+ million execs with improved fuzzer on New Years day.

Please try using main branch and report any issues. 🙏 Thanks!

[fxamacker]

v2.6.0-rc.0 was tagged. For more details, see
https://github.com/fxamacker/cbor/releases/tag/v2.6.0-rc.0

[fxamacker]

Closed by https://github.com/fxamacker/cbor/releases/tag/v2.6.0 (same as v2.6.0-rc.0).