mirrors/arti.git/crates/tor-llcrypto/Cargo.toml, branch arti-v0.3.0

Bump the version of every* crate to 0.3.0

2022-05-06T14:03:15Z

* Except for safelog and fs-mistrust, which are new.

Upgrade to AES 0.8

2022-04-26T16:16:22Z

Now that we require Rust 1.56, we can upgrade to AES 0.8. This forces us to have some slight API changes. We require cipher 0.4.1, not cipher 0.4.0, since 0.4.0 has compatibility issues with Rust 1.56.

Bump every crate's edition to 2021.

2022-04-25T17:05:31Z

This is an automated change made with a perl one-liner and verified with grep -L and grep -l. Some warnings are introduced with this change; they will be removed in subsequent commits. See arti#208 for older discussion on this issue.

Add 'rust-version = "1.56"' to every Cargo.toml file.

2022-04-25T17:04:31Z

This change was made automatically with a perl one-liner, and confirmed with `grep -L`. The `rust-version` field itself was introduced in 1.56.0.

Reformat all not-yet-reformatted Cargo.toml files.

2022-04-25T17:04:31Z

There are no semantic changes here; only formatting. This is in preparation for other changes (wrt MSRV and edition)

Bump all arti, tor crates to 0.2.0

2022-04-01T13:15:18Z

Not all of these strictly need to be bumped to 0.2.0; many could go to 0.1.1 instead. But since everything at the tor-rtcompat and higher layers has had breaking API changes, it seems not so useful to distinguish. (It seems unlikely that anybody at this stage is depending on e.g. tor-protover but not arti-client.)

Bump all crates to 0.1.0

2022-03-01T13:59:34Z

Bump all crate versions to 0.0.3.

2022-01-11T14:40:32Z

Minimize the required version for each dependency.

2022-01-08T00:08:58Z

I found these versions empirically, by using the following process: First, I used `cargo tree --depth 1 --kind all` to get a list of every immediate dependency we had. Then, I used `cargo upgrade --workspace package@version` to change each dependency to the earliest version with which (in theory) the current version is semver-compatible. IOW, if the current version was 3.2.3, I picked "3". If the current version was 0.12.8, I picked "0.12". Then, I used `cargo +nightly upgrade -Z minimal-versions` to downgrade Cargo.lock to the minimal listed version for each dependency. (I had to override a few packages; see .gitlab-ci.yml for details). Finally, I repeatedly increased the version of each of our dependencies until our code compiled and the tests passed. Here's what I found that we need: anyhow >= 1.0.5: Earlier versions break our hyper example. async-broadcast >= 0.3.2: Earlier versions fail our tests. async-compression 0.3.5: Earlier versions handled futures and tokio differently. async-trait >= 0.1.2: Earlier versions are too buggy to compile our code. clap 2.33.0: For Arg::default_value_os(). coarsetime >= 0.1.20: exposed as_ticks() function. curve25519-dalek >= 3.2: For is_identity(). generic-array 0.14.3: Earlier versions don't implement From<&[T; 32]> httparse >= 1.2: Earlier versions didn't implement Error. itertools at 0.10.1: For at_most_once. rusqlite >= 0.26.3: for backward compatibility with older rustc. serde 1.0.103: Older versions break our code. serde_json >= 1.0.50: Since we need its Value type to implement Eq. shellexpand >= 2.1: To avoid a broken dirs crate version. tokio >= 1.4: For Handle::block_on(). tracing >= 0.1.18: Previously, tracing_core and tracing had separate LevelFilter types. typenum >= 1.12: Compatibility with rust-crypto crates x25519-dalek >= 1.2.0: For was_contributory(). Closes #275.

Upgrade to digest v0.10.0

2021-12-08T01:33:46Z

We generally try to track the latest rust-crypto traits when we can: fortunately, this upgrade didn't break much, considering.