Source: libcbor
Version: 0.8.0-2
Severity: wishlist

Dear maintainer,

there are several new upstream releases available at
<https://github.com/PJK/libcbor/releases>, their changes read

| 0.10.2 (2023-01-31)
| - Fixed minor test bug causing failures for x86 Linux (discovered by
|   trofi)
|   - Actual libcbor functionality not affected, bug was in the test suite
| - Made tests platform-independent
| 
| 0.10.1 (2022-12-30)
| - Fix a regression in cbor_serialize_alloc that caused serialization of
|   zero-length strings and bytestrings or byte/strings with zero-length
|   chunks to fail (discovered by martelletto)
| 
| 0.10.0 (2022-12-29)
| - Make the buffer_size optional in cbor_serialize_alloc [#205] (by
|   hughsie)
| - BREAKING: Improved half-float encoding for denormalized numbers.
|   [#208] (by ranvis)
|   - Denormalized half-floats will now preserve data in the mantissa
|   - Note: Half-float NaNs still lose data (#215)
| - BUILD BREAKING: Minimum CMake version is 3.0 [#201] (by thewtex@)
|   - See https://repology.org/project/cmake/versions for support; the
|     vast majority of users should not be affected.
| - Fix a potential memory leak when the allocator fails during array or
|   map decoding [#224] (by James-ZHANG)
| - Fix a memory leak when the allocator fails when adding chunks to
|   indefinite bytestrings. (discovered by James-ZHANG)
| - Fix a memory leak when the allocator fails when adding chunks to
|   indefinite strings
| - Potentially BUILD BREAKING: Add nodiscard attributes to most functions
|   - Warning: This may cause new build warnings and (in rare cases,
|     depending on your configuration) errors
| - BREAKING: Fix cbor_copy leaking memory and creating invalid items when
|   the allocator fails.
|   - Previously, the failures were not handled in the interface. Now,
|     cbor_copy may return NULL upon failure; clients should check the
|     return value
| - Fix cbor_build_tag illegal memory behavior when the allocator fails
| - Add a new cbor_serialized_size API
| - Reworked cbor_serialize_alloc to allocate the exact amount of memory
|   necessary upfront
|   - This should significantly speed up cbor_serialize_alloc for large
|     items by avoiding multiple reallocation iterations
|   - Clients should not use the return value of cbor_serialize_alloc. It
|     may be removed in the future.
| - BUILD BREAKING: Deprecate CBOR_CUSTOM_ALLOC
|   - cbor_set_allocs will always be enabled from now on
|   - Note: The flag will be kept as a no-op triggering a warning when
|     used for one version and then removed completely
| 
| 0.9.0 (2021-11-14)
| - Improved pkg-config paths handling [#164] (by jtojnar@)
| - Use explicit math.h linkage [#170]
| - BREAKING: Fixed handling of items that exceed the host size_t range
|   [#186]
|   - Callbacks for bytestrings, strings, arrays, and maps use uint64_t
|     instead of size_t to allow handling of large items that exceed
|     size_t even if size_t < uint64_t
|   - cbor_decode explicitly checks size to avoid overflows (previously
|     broken, potentially resulting in erroneous decoding on affected
|     systems)
|   - The change should be a noop for 64b systems
| - Added a Bazel build example [#196] (by andyjgf@)

Well, those contain quite some changes marked as BREAKING which might
complicate things.

Please update the package when you think it is due time.

Cheers,
Flo

Attachment: signature.asc
Description: PGP signature

Reply via email to