Skip to content

upgrade zlib-rs to version 0.5.1 #490

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 7, 2025

Conversation

folkertdev
Copy link
Contributor

https://github.com/trifectatechfoundation/zlib-rs/releases/tag/v0.5.1

Fixes some minor bugs and improves performance.

Copy link
Member

@Byron Byron left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks a lot!

@Byron Byron merged commit ac4d950 into rust-lang:main Jun 7, 2025
15 checks passed
@@ -468,7 +468,7 @@ mod c_backend {
#[cfg(feature = "zlib-ng")]
const ZLIB_VERSION: &str = "2.1.0.devel\0";
#[cfg(all(not(feature = "zlib-ng"), feature = "zlib-rs"))]
const ZLIB_VERSION: &str = "1.3.0-zlib-rs-0.5.0\0";
const ZLIB_VERSION: &str = "1.3.0-zlib-rs-0.5.1\0";
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just realised that if it wasn't for this string, flate2 wouldn't need a release if zlib-rs increases its patch level.
Something I am wondering about is if this lock-step releasing is truly required for everything to work?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As far as I can tell, the only thing that zlib-rs actually cares about is that the first byte of the string is a '1' character.

@Byron
Copy link
Member

Byron commented Jun 7, 2025

A new release is now available: https://github.com/rust-lang/flate2-rs/releases/tag/1.1.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants