You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
0.11.0 (2024-02-04)
---------------------
- [Updated documentation to refer to RFC 8949](PJK/libcbor#269)
- Improvements to `cbor_describe`
- [Bytestring data will now be printed as well](PJK/libcbor#281) by [akallabeth](https://github.com/akallabeth)
- [Formatting consistency and clarity improvements](PJK/libcbor#285)
- [Fix `cbor_string_set_handle` not setting the codepoint count](PJK/libcbor#286)
- BREAKING: [`cbor_load` will no longer fail on input strings that are well-formed but not valid UTF-8](PJK/libcbor#286)
- If you were relying on the validation, please check the result using `cbor_string_codepoint_count` instead
- BREAKING: [All decoders like `cbor_load` and `cbor_stream_decode` will accept all well-formed tag values](PJK/libcbor#308) (bug discovered by [dskern-github](https://github.com/dskern-github))
- Previously, decoding of certain values would fail with `CBOR_ERR_MALFORMATED` or `CBOR_DECODER_ERROR`
- This also makes decoding symmetrical with serialization, which already accepts all values
Describe the bug
Documentation references RFC 7049, which has been replaced by RFC 8949 (STD94) a couple of years ago.
To Reproduce
(Read the documentation.)
Expected behavior
Update the documentation to use RFC 8949.
In the process, check that clarifications made in RFC 8949 actually are addressed (e.g., deterministic encoding) — https://www.rfc-editor.org/rfc/rfc8949#name-changes-from-rfc-7049 might help here.
Environment
"Documentation for version 0.10.1, updated on Jan 08, 2023."
The text was updated successfully, but these errors were encountered: