Repository navigation
Release new version to include latest patch? #23
Description
We were hit by this bug that got recently fixed by #22. Would it be possible to make a new release including it?
I pushed this gem for our case as a temporary measure, but it would be great to be able to use the official one.
By the way, thanks so much to @wanabe for fixing this one 🙏. The possibility of zlib silently writing corrupted data is a serious one and, depending on the scenario, can cause data-loss.
Activity
hsbt commentedon Mar 15, 2021
I'm considering to release it before releasing Ruby 3.0.1.
cjf2xn commentedon Oct 13, 2021
@hsbt do you know when you can cut a new release that includes #22?
This issue has bitten us quite a few times and it results in data loss as @jorgemanrubia mentioned.
hsbt commentedon Oct 14, 2021
I cut of 2.1.0 release from dd593ac