Release aes v0.9.1

[newpavlov]

Fixed

• Minimal version of zeroize dependency (#562)
• Build warnings on AArch64 targets (#562)

[newpavlov]

@tarcieri
Note that I think it's worth to yank v0.9.0 to fix minimal versions build in downstream crates relying on the zeroize feature.

[dvzrv]

Note that I think it's worth to yank v0.9.0 to fix minimal versions build in downstream crates relying on the zeroize feature.

Hm, could you elaborate why yanking the 0.9.0 version was necessary? It is quite disruptive to downstream CI as well 😅

[newpavlov]

Because we test minimal dependency versions as part of our CI tests, so downstream crates could pull aes v0.9.0 and incorrect version of zeroize which results in a compilation error since aes uses function introduced only in zeroize v1.8. So we either have to pin aes to v0.9.1 in all downstream crates or simply yank v0.9.0 as a "buggy" version.

It is quite disruptive to downstream CI as well

It should not be disruptive. If you commit Cargo.lock, then yanking should not affect you, if not, then v0.9.1 should be pulled by default.

[joshsleeper]

It should not be disruptive. If you commit Cargo.lock, then yanking should not affect you,

huh, I was gonna say that it would specifically and explicitly affect folks who commit and install from Cargo.lock if said lockfile has v0.9.0 locked... but TIL cargo tolerates locked + yanked packages with a warning to avoid breakage apparently

Cargo will not use a yanked version for any new project or checkout without a pre-existing lockfile, and will generate an error if there are no longer any compatible versions for your crate.

https://doc.rust-lang.org/cargo/commands/cargo-yank.html