mirrors/arti.git/crates/tor-config-path, branch arti-v1.4.5

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

2025-07-07T17:41:41Z

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

Temporarily suppress mismatched_lifetime_syntaxes.

2025-07-07T15:50:04Z

See #2060.

tor-config-path: Removed dependency on `once_cell`

2025-06-15T02:11:18Z

- Replaced `once_cell::sync::Lazy` with `std::sync::LazyLock`. Signed-off-by: hashcatHitman <3924-hashcatHitman@gitlab.torproject.org>

release: Bump all tor-/arti- crates to 0.31.0.

2025-06-05T10:33:57Z

This was done using: for crate in $(./maint/list_crates | grep -P '^tor-|^arti-'); do cargo set-version -p $crate 0.31.0 done

./maint/cargo_sort: Run cargo-sort on the entire workspace.

2025-05-27T13:32:26Z

The [latest version] of `cargo-sort` is more opinionated than the previous one, and is now causing the `rust-checks` job to fail on `main`. This commit applies the fixes needed to satisfy the new `cargo-sort` rules. These changes were generated by running `cargo sort --workspace` several times, until `cargo sort --check --workspace` finally succeeded (it couldn't fix all the errors in one go, for some reason). I have omitted the changes `cargo-sort` made to the top-level `Cargo.toml`, to preserve the topological ordering of the workspace members. Closes #2014 [latest version]: https://github.com/DevinR528/cargo-sort/blob/f066ae80e5e6f5c1d8f0e2b8099461dcb97d9656/changelog.md#200

All crates: bump rust-version to 1.83.

2025-05-13T18:46:28Z

release: Bump all unstable tor/arti crates to 0.30.0

2025-05-01T16:22:28Z

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

Remove semver.md files post-release.

2025-04-01T11:27:04Z

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

2025-03-31T17:59:51Z

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

AF_UNIX terminology: Rename two error structs

2025-03-24T13:58:54Z

We change `NoUnixAddressSupport` to `NoAfUnixSocketSupport` because it doesn't make much sense to talk about support for the addresses separately from support for the sockets.