v4.0.0

What's Changed

• Update zbus to v4 by @liff in #75
• Run CI with all feature variants by @liff in #79

Full Changelog: v3.1.0...v4.0.0

v3.1.0

Changed

• Update minimum serde version by @alex in #68
• Update MSRV to 1.64 by @complexspaces in #76
• Update RustCrypto dependencies by @liff in #74 (previously #59 by @nc7s)

Added

• Added unlock_all method by @nikarh in #73

Full Changelog: v3.0.1...v3.1.0

v3.0.1

• Fix docs.rs builds

v3.0.0

• Updated dependencies where reasonable
• It is now possible to choose between RustCrypto and OpenSSL cryptography providers with feature flags.
• Bumped MSRV to 1.60
• BREAKING: Updated to zbus 3.0. This changes error types and public path fields.
• BREAKING: The types exported from the crate root are now entirely async. Blocking functions have been moved into the blocking module.
• BREAKING: Error::Crypto now contains a &'static str instead of a String.
• BREAKING: SecretService::search_items now takes a HashMap<&str, &str> instead of Vec<(&str, &str)> for the attributes.
• BREAKING: The SecretService::new() method was renamed to SecretService::connect() to be more accurate.
• BREAKING: Error is now marked as #[non_exhaustive] to allow for additions to be made more easily in the future.
• BREAKING: Several dead error variants were pruned.
• BREAKING: search_items now returns both locked and unlocked items. If an unlocked item isn't present
  in the list, it must be unlocked manually.
• BREAKING: It is now required to choose a feature set in order to use the crate. See the README for more details.

v2.0.2

This version bumps the zbus dependency to a new minimum of v1.9.2.
This is important because zbus v1.9.2 depends on nix v0.20.2,
which is the first release of nix not to contain the security
vulnerability described at https://rustsec.org/advisories/RUSTSEC-2021-0119

v2.0.1

• Updated crate's Rustdoc link

v2.0.0

• dbus replaced by zbus, PURE RUST!
• update to 2018 edition
• BREAKING: SsError renamed to Error
• BREAKING: variants added to Error
• BREAKING: attributes are now HashMap<&str, &str> or HashMap<String, String> instead of Vec<(&str, &str)>. Not sure why I decided this way back when, but it could cause unexpected behavior for user: when the Vec was transformed to HashMap internally, tuples could be lost if the keys were the same.
• BREAKING: Collection::new and Item::new are now private (although I don't think it was possible to use them anyways)

v1.1.3

• update deps

v1.1.2

• update rand

v1.1.1

update deps