Yank both 2.6.0 and 2.6.1 as they both introduce a breaking change and republish as 3.0.0

[jqnatividad]

Just making this request explicit based on the #332 thread - as both 2.6.0 and 2.6.1 introduce a breaking change, and per https://semver.org/ guidance - requires a major version.

[jqnatividad]

Doing so should allow zip 2.5 ecosystem users (which far outnumber zip 2.6 users) to remove workarounds, and for the few that have upgraded to 2.6, to simply just bump their zip to 3.0.0.

[prophittcorey]

This would be ideal. If this change goes out, it would fix all of the packages that didn't pin specifically to 2.5.0.

I've opened a change in a crate that depends on 2.5.0 (tafia/calamine#497) and the maintainer doesn't seem to be around. That's not a unique experience, it's happening to many crates.

If zip yanks 2.6 and 2.6.1 and republishes those changes as 3.0, all currently broken crates will be fixed.

[simnalamburt]

I agree with this as well. zip v2.6.0 and v2.6.1 should be yanked. A large number of developers are currently forced to pin the version to 2.5.0 just to avoid issues. Please take appropriate action.

[VimCommando]

When I upgraded my crate from 2.2.2 to 2.6.1 it also broke my container builds.

Since I'm deploying with a distroless container image, by design there are very minimal system libraries. Version 2.6.1 somehow introduced lzma-sys into the dependency chain (found it in cargo.lock). With lzma enabled, the container would build, but always fail at runtime with:

/usr/local/bin/esdiag: error while loading shared libraries: liblzma.so.5: cannot open shared object file: No such file or directory

I had to use default-features = false on zip2 in the Cargo.toml to drop the lzma feature and only opt-in to what I was using. This allow my containers to build and as expected again.

[tylerasai]

Come on guys let's get this going.

[Leandros]

Issues are happening downstream due to this, see zip-extract: MCOfficer/zip-extract#38

[k-bx]

@Pr0methean any chance on making this happen? It broke quite a number of upgrades

[Pr0methean]

I'll do this once #345 is merged, since creating a new release while the build in master is failing would risk even worse issues.