mirrors/arti.git/crates/tor-cell, branch arti-v2.0.0

release: Bump `arti-` and `tor-` crates to 0.39.0

2026-02-02T17:03:49Z

Done via: ``` for crate in $(./maint/list-crates | rg '^(tor|arti-)'); do cargo set-version -p $crate 0.39.0 done ```

Merge branch 'main' into 'main'

2026-02-02T14:51:20Z

fix(minver): Update paste dependency to be minver compatible See merge request tpo/core/arti!3610

maint/add_warning: Run script to add new warning

2026-01-27T18:05:36Z

This adds the lint to all our crates.

fix(minver): Update paste dependency to be minver compatible

2026-01-26T17:22:16Z

proto: Authenticate a relay channel

2026-01-22T16:16:44Z

This commit is a bit loaded but it is coherent. First, we set Eq and PartialEq to the channel message Authenticate so we can compare it with the one we expected. Second, the AuthenticationCell enum is introduced to store either an AUTH_CHALLENGE or an AUTHENTICATE since one side of the handshake can only have one. This allows us to store one or the other in UnverifiedRelayChannel. Depending on what we have, the authentication process is different as it dictates which side we are on (initiator vs responder). Keep in mind that the handshake code enforces receiving a AUTH_CHALLENGE along side CERTS. And same goes for AUTHENTICATE which means that if we have an AUTH_CHALLENGE in the UnverifiedRelayChannel, it is certain that the other side wants to authenticate and we are the initiator. Finally, the sending of CERTS and AUTHENTICATE by the initiator is now in UnverifiedRelayChannel::check() done right after verifying the channel CERTS and holding a "VerifiedChannel" object. This means that the last piece, sending the `NETINFO` by the initiator will be done in the check() but in a future commit. This leaves the VerifiableChannel::finish() to send nothing and only finalize the channel with the NETINFO (canonicity). Signed-off-by: David Goulet

cargo: Update `arti-` and `tor-` to `0.38.0`

2026-01-12T12:32:35Z

Done using the following: ```bash for crate in $(./maint/list_crates | rg '^(tor|arti-)'); do cargo set-version -p $crate 0.38.0 done ```

Remove unnecessary `doc(cfg(...))` attributes

2025-12-05T02:40:50Z

Fixes part of #2193. (Edits from nickm: I selected the cases here that I could verify were correct from immediate context.) Edited-by: Nick Mathewson

Pin our derive-deftly version to ~1.6.0 everywhere

2025-12-03T18:56:38Z

We are supposed to pin whenever we enable the `beta` cargo feature, see https://docs.rs/derive-deftly/latest/derive_deftly/doc_changelog/index.html#beta-features Empirically, we somehow failed to do that in tor-circmgr. In practice not pinning makes little difference since cargo wants to pick the same version everywhere, but we should be correct. But it is more maintainable to pin everywhere.

Update to derive-deftly 1.6.0

2025-12-03T18:22:58Z

This has: * Fixes to hygiene spans from the new modules feature, needed for my WIP netdoc encoder derive. * A substantially richer `${error }` construct.

Bump all the unstable tor- and arti- crates to 0.37.0.

2025-12-02T11:07:59Z

Done using: ``` for crate in $(./maint/list_crates | rg '^(tor|arti-)'); do cargo set-version -p $crate 0.37.0 done