self_update pulls in zipsign-api even when signatures feature is not enabled

[amtep]

Hi, I was investigating what pulls in base64ct (which requires edition 2024), and it turned out to be self_update via zipsign-api.
But self_update is not supposed to pull that in because I don't use the signatures feature.

Here's the bit from my Cargo.toml:

[target.'cfg(target_os = "windows")'.dependencies]
self_update = { version = "0.42", features = [
    "archive-zip",
    "compression-zip-deflate",
] }

[target.'cfg(target_os = "linux")'.dependencies]
self_update = { version = "0.42", features = [
    "archive-tar",
    "compression-flate2",
] }

I'd love to reduce my dependency count a little here.

I looked at self_update's Cargo.toml and I can't figure out what's going wrong.

[amtep]

I should provide the actual error message too:

Downloaded base64ct v1.8.0
error: failed to parse manifest at `/home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/base64ct-1.8.0/Cargo.toml`

Caused by:
  feature `edition2024` is required

  The package requires the Cargo feature called `edition2024`, but that feature is not stabilized in this version of Cargo (1.84.1 (66221abde 2024-11-20)).
  Consider trying a newer version of Cargo (this may require the nightly release).
  See https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#edition-2024 for more information about the status of this feature.
Error: Process completed with exit code 101.