Releases: thecoolwinter/CBOR
1.1.2
The Fifth One
- Fixes a false positive
'found an integer encoded as larger than necessary'error for specifically the number24. - Fixes an incorrect header size for large collections (anything larger than 65,536 elements).
- Fixes a build error on iOS, tvOS, and watchOS for anyone building the entire package instead of just the public
CBORtarget (such as swiftpackageindex).
Full Changelog: 1.1.1...1.1.2
1.1.1
The Fourth One
Fixes a build error on some Apple platforms where access to Int128 is an issue.
Notes from the previous release:
Introduces a new DAG-CBOR Decoder and Encoder. These are compatible with the IPLD spec. Internally, they just configure the correct encoding/decoding parameters for encoding and decoding DAG-CBOR data. To that end, this release adds numerous more flags for configuring how strict the decoder is and how the encoder writes your data.
Full Changelog: 1.1.0...1.1.1
1.1.0
The Third One
Introduces a new DAG-CBOR Decoder and Encoder. These are compatible with the IPLD spec. Internally, they just configure the correct encoding/decoding parameters for encoding and decoding DAG-CBOR data. To that end, this release adds numerous more flags for configuring how strict the decoder is and how the encoder writes your data.
What's Changed
- Fix typo of Usage in README by @beforeold in #1
- DAG-CBOR by @thecoolwinter in #2
New Contributors
- @beforeold made their first contribution in #1
- @thecoolwinter made their first contribution in #2
Full Changelog: 1.0.1...1.1.0
1.0.1
The Second One
Introduces a new API for decoding packed CBOR blobs that were not encoded as a single array. Some encoders choose to encode multiple top-level items as just that, multiple concatenated top-level items. This library now supports decoding those blobs using the new CBORDecoder().decodeMultiple(_:from:) method.
This method decodes as many top-level items of type T: Decodable until either the data has been read entirely or an error is encountered. This method has been added to all fuzz testing, and new tests have been introduced ensuring it's functional and safe. This is not a breaking change.
Documentation: Swift Package Index
Full Changelog: 1.0.0...1.0.1