mirrors/arti.git/examples/gsoc2023/connection-checker, 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 ```

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 ```

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

maint: bump minor versions of all published crates

2025-10-29T19:32:37Z

```bash readarray -t publish < <(cargo metadata --format-version 1 | jq -r '.packages[] | select((.id | startswith("path+file:///")) and (.rust_version != null) and (.publish == null or .publish == true or .publish != [])) | .name') for package in "${publish[@]}"; do echo "$package:"; cargo set-version --bump minor -p "$package"; done ```

release: Bump versions in examples/ and maint/

2025-10-02T15:17:55Z

release: Run fixup-features.

2025-10-01T18:36:58Z

Require tracing-subscriber 0.3.20

2025-09-02T12:53:23Z

Fixes RUSTSEC-2025-0055.

proto: Move the `stream` module under `client` (breaking).

2025-08-18T16:09:04Z

The `stream` module is client-specific, for the most part, so I am moving it under `client`. Later on, we will factor out the parts that can be shared with the relay implementation. Note: this is a breaking change as the deleted `stream` module was `pub`. We could've kept the module and reexported from it the public types from `tor_proto::client::stream`, but I think it's better to have this `client` namespacing, because it makes the separation between the client and relay parts clearer.

Switch Cargo.toml files to edition 2024.

2025-08-07T15:28:36Z

First, run ``` git grep -l "^edition =" | xargs perl -i -pe 's/^edition *=.*/edition = "2024"/;' ``` Second, manually verify that all Cargo.toml files have changed, and nothing else has changed. Third, run cargo fmt again.

proto: abolish path_ref() in favor of all_paths().

2025-08-05T18:23:02Z

Until now, we've been using `ClientCirc::path_ref()` to get the *only* path of a circuit. Now that `ClientCirc` is a handle to a tunnel reactor (which may or may not be multi-path), we need to decide for each call site of `path_ref()`, if we actually want *all* paths in the tunnel, or if we expect the tunnel to be single-path and thus want the *only* path in the tunnel. I've added two new APIs to address this: `all_paths()`, for getting all the paths in the tunnel, and `single_path()` for getting the only path in the tunnel, or an error if the tunnel is single-path.