chore: release v3.0.0

[Pr0methean]

🤖 New release

• zip: 2.6.1 -> 3.0.0 (⚠ API breaking changes)

⚠ zip breaking changes

--- failure feature_missing: package feature removed or renamed ---

Description:
A feature has been removed from this package's Cargo.toml. This will break downstream crates which enable that feature.
        ref: https://doc.rust-lang.org/cargo/reference/semver.html#cargo-feature-remove
       impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.41.0/src/lints/feature_missing.ron

Failed in:
  feature proc-macro2 in the package's Cargo.toml
  feature deflate-zlib in the package's Cargo.toml
  feature deflate-miniz in the package's Cargo.toml
  feature deflate-zlib-ng in the package's Cargo.toml
  feature flate2 in the package's Cargo.toml

Changelog

3.0.0 - 2025-05-14

🐛 Bug Fixes

• return correct offset in SeekableTake::seek (#342)
• When only zopfli is available, decompression of deflate should not be possible (#348)
• Specify flate2 dependency of the deflate-flate2 feature. (#345)

⚙️ Miscellaneous Tasks

• fix typo
• remove deflate-flate2 dependency on specific backend
• [breaking] Drop deprecated deflate-miniz feature flag (#351)

---

This PR was generated with release-plz.

[Pr0methean]

Canceling CI to await a version bump to 3.0.0 once #351 is merged.

[joshtriplett]

@Pr0methean Please don't have deflate-flate2 depend on the flate2/rust_backend feature. That makes it difficult for users who want to use a different flate2 backend and don't want to build the (slow) rust_backend.

Previously, deflate-flate2 seemed to be intended as a "just use flate2 but let me specify the backend" feature, whereas e.g. features like flate2-zlib-ng pulled in specific backends.

Alternatively, if you want to make deflate-flate2 be more automatic, consider having deflate-flate2 depend on flate2/zlib-rs (which is much faster), and then providing a deflate-flate2-nobackend which just depends on dep:flate2 and lets the user pick a backend. If you do that then you could probably drop all the other backend-specific features.

[Pr0methean]

@joshtriplett Fixed in 7762944.

[joshtriplett]

@Pr0methean I've got an alternate PR that I think a new major version is the perfect time for. Submitting that now...

[joshtriplett]

#352

Needs a new major version because it modifies and drops features, and modifies the defaults. And since this is a new major version, it's the perfect time to switch the default backend, because people will be switching to the new version deliberately rather than having it show up in a cargo update.