Bump zstandard from 0.17.0 to 0.21.0 in /tools

[dependabot]

Bumps zstandard from 0.17.0 to 0.21.0.

Release notes

Sourced from zstandard's releases.

0.20.0

Backwards Compatibility Notes

• This will likely be the last release officially supporting Python 3.6. Python 3.6 is end of life as of 2021-12-23.

Changes

• Bundled zstd library upgraded from 1.5.2 to 1.5.4.
• Use of the deprecated ZSTD_copyDCtx() was removed from the C and Rust backends.

0.19.0

Bug Fixes

• The C backend implementation of ZstdDecompressionObj.decompress() could have raised an assertion in cases where the function was called multiple times on an instance. In non-debug builds, calls to this method could have leaked memory.

Changes

• PyPy 3.6 support dropped; Pypy 3.8 and 3.9 support added.
• Anaconda 3.6 support dropped.
• Official support for Python 3.11. This did not require meaningful code changes and previous release(s) likely worked with 3.11 without any changes.
• CFFI's build system now respects distutils's compiler.preprocessor if it is set. (#179)
• The internal logic of ZstdDecompressionObj.decompress() was refactored. This may have fixed unconfirmed issues where unused_data was set prematurely. The new logic will also avoid an extra call to ZSTD_decompressStream() in some scenarios, possibly improving performance.
• ZstdDecompressor.decompress() how has a read_across_frames keyword argument. It defaults to False. True is not yet implemented and will raise an exception if used. The new argument will default to True in a future release and is provided now so callers can start passing read_across_frames=False to preserve the existing functionality during a future upgrade.
• ZstdDecompressor.decompress() now has an allow_extra_data keyword argument to control whether an exception is raised if input contains extra data. It defaults to True, preserving existing behavior of ignoring extra data. It will likely default to False in a future release. Callers desiring the current behavior are encouraged to explicitly pass allow_extra_data=True so behavior won't change during a future upgrade.

Changelog

Sourced from zstandard's changelog.

0.21.0 (released 2023-04-16)

Backwards Compatibility Notes

• Support for Python 3.6 has been dropped. Python 3.7 is the minimum supported Python version.

Changes

• Bundled zstd library upgraded from 1.5.4 to 1.5.5.
• PyO3 Rust crate upgraded from 0.15 to 0.18.
• CI environment changed from Ubuntu 20.04 -> 22.04, Windows 2019 -> 2022, macOS 11 -> macOS 12.
• C types now use PyType_Spec and corresponding APIs. (#187) Contributed by Mike Hommey.

0.20.0 (released 2023-02-20)

Backwards Compatibility Notes

• This will likely be the last release officially supporting Python 3.6. Python 3.6 is end of life as of 2021-12-23.

Changes

• Bundled zstd library upgraded from 1.5.2 to 1.5.4.
• Use of the deprecated ZSTD_copyDCtx() was removed from the C and Rust backends.

0.19.0 (released 2022-10-29)

Bug Fixes

• The C backend implementation of ZstdDecompressionObj.decompress() could have raised an assertion in cases where the function was called multiple times on an instance. In non-debug builds, calls to this method could have leaked memory.

Changes

• PyPy 3.6 support dropped; Pypy 3.8 and 3.9 support added.

... (truncated)

Commits

• 80be4ef global: release version 0.21.0
• 124190d rust: update dependencies to latest
• 0def67f global: reflect upgrade to zstd 1.5.5
• edd8869 zstd: upgrade vendored zstd to 1.5.5
• 7f0c3aa docs: document that C types now use PyType_Spec and friends.
• 727b00d Use PyType_Spec to define types instead of PyTypeObject: ZstdBufferWithSegmen...
• e4d2b18 Use PyType_Spec to define types instead of PyTypeObject: ZstdBufferSegments
• 2a145db Use PyType_Spec to define types instead of PyTypeObject: ZstdBufferSegment
• 1c00b79 Use PyType_Spec to define types instead of PyTypeObject: ZstdBufferWithSegments
• 818caac Use PyType_Spec to define types instead of PyTypeObject: FrameParameters
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)