mirrors/arti.git/crates/tor-proto/Cargo.toml, branch arti-v1.1.9

Patchlevel bumps to crates whose dependencies just changed.

2023-10-02T18:55:03Z

(The only change in these crates is that their dependencies changed.)

Minor-version bumps, for crates with breaking changes.

2023-10-02T18:51:27Z

Patchlevel bumps, with dependents affected.

2023-10-02T18:48:11Z

Remove direct dependency on generic-array

2023-09-28T14:59:29Z

Instead of tying ourselves to a particular version of the generic-array crate, we now always use the version re-exported by our RustCrypto crates. This lets us avoid the possibility of version mismatch. (Originally I had planned to upgrade to generic-array 1.0, but then I found that we were not actually using it.)

Update patchlevel for crates with nontrivial changes.

2023-09-05T16:22:19Z

These are: ``` hashx equix tor-async-utils tor-error tor-config tor-rtmock tor-llcrypto tor-bytes tor-hscrypto tor-hspow tor-cert tor-linkspec tor-cell tor-proto tor-netdoc tor-netdir tor-chanmgr tor-guardmgr tor-dirmgr tor-keymgr tor-hsclient tor-hsservice arti-client arti ```

Upgrade to visibility 0.1.0

2023-09-05T12:04:26Z

proto: methods to wait until a channel/circuit is shut down.

2023-08-04T17:37:28Z

The implementation here is perhaps excessively simple: we put a `oneshot::Sender` in the `Reactor` object, and a `Shared` in the circuit or channel. When the reactor is dropped, any copy of the `Shared` will yield `Err(Cancelled)`. I'm marking these methods as experimental because I'm not sure I've thought of all the implications here, and we might want to change things around. Down the road, these methods might want to yield a `Result<>` indicating why the reactor was shut down. This feature was inspired by a request from Saksham Mittal, and a felt need while working on !1472.

tor-proto: Add ClientCirc::start_conversation().

2023-08-04T12:08:31Z

This will enable hidden services to send `RENDEZVOUS1` messages to the `N`th hop of the circuit rather than the `N + 1`th virtual one (which can only used after the client and service have completed the introduction handshake). This also deprecates `start_conversation_last_hop`. Closes #959

Increment patchlevel versions of crates with minor changes

2023-08-01T14:57:55Z

These crates are at version 0.x.y, so we don't need to distinguish new-feature changes from other changes: ``` tor-basic-utils fs-mistrust tor-error tor-geoip tor-checkable tor-linkspec tor-netdoc tor-netdir tor-persist tor-ptmgr tor-hsservice ``` This crate has a breaking change, but only when the semver-breaking feature `experimental-api` is enabled: ``` tor-config ``` This crate is at version 1.x.y, but has no new public APIs, and therefore does not need a minor version bump: ``` arti ```

Update minor versions on crates that have had breaking changes

2023-08-01T14:51:25Z

These crates had first-order breaking changes: ``` retry-error tor-keymgr tor-proto tor-hsclient tor-rtmock ``` Additionally, these broke because they re-exposed RetryError: ``` tor-circmgr ``` Additionally, these broke because they may re-expose something from tor-proto: ``` arti-client tor-chanmgr tor-dirclient tor-dirmgr tor-guardmgr ``` Additionally, these broke for other fiddly reasons: `tor-ptmgr` implements traits from tor-chanmgr, which has a breaking change above. `arti-hyper` exposes types from arti-client in its API.