mirrors/arti.git/crates/tor-dirmgr/Cargo.toml, branch arti-v1.4.4mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.4.42025-06-05T10:33:57Zrelease: Bump all tor-/arti- crates to 0.31.0.2025-06-05T10:33:57ZAlexander Hansen Færøyahf@torproject.org2025-06-05T10:33:57Zurn:sha1:95180f80d7ab574a95368f3bca1e7b78555d479a
This was done using:
for crate in $(./maint/list_crates | grep -P '^tor-|^arti-'); do
cargo set-version -p $crate 0.31.0
done
release: Bump crates non-arti/non-tor crates with functional changes.2025-06-05T10:24:54ZAlexander Hansen Færøyahf@torproject.org2025-06-05T10:24:54Zurn:sha1:7794a5b1c60c694f1fc0c9d0de2e59ae1bdc31de
This is done using:
cargo set-version --bump patch -p fs-mistrust
cargo set-version --bump patch -p equix
cargo set-version --bump patch -p fslock-guard
./maint/cargo_sort: Run cargo-sort on the entire workspace.2025-05-27T13:32:26ZGabriela Moldovangabi@torproject.org2025-05-23T13:54:02Zurn:sha1:03885fdbf4ea19b9215e05cc557372758359f44d
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:28ZNick Mathewsonnickm@torproject.org2025-05-13T18:46:28Zurn:sha1:88e911acd4bb70bf1da0fc71d77b51cb6abde478release: Bump all unstable tor/arti crates to 0.30.02025-05-01T16:22:28ZWesley Aptekar-Casselsme@wesleyac.com2025-05-01T15:55:57Zurn:sha1:770aaa9648d42835b2c6b3b29f4051d287ddba88
```
for crate in $(./maint/list_crates | rg '^(tor|arti-)'); do
cargo set-version -p $crate 0.30.0
done
```
chore: Run fixup-features.2025-04-30T15:49:52ZWesley Aptekar-Casselsme@wesleyac.com2025-04-30T14:26:40Zurn:sha1:da4308744bf59b50dfcc28a438fda047a115812d
cargo run -p fixup-features -- --exclude examples/ --exclude maint/ Cargo.toml
The following features in arti-ureq were manually added to full or
marked non-additive:
* rustls
* native-tls
* tokio
* async-std
Update rand requirement to 0.9.12025-04-29T22:52:26ZNick Mathewsonnickm@torproject.org2025-04-29T19:04:27Zurn:sha1:fc0810c1091b2ec606111ae94e726cf5f7b10b38
(This is going to be a _requirement_,
since rand 0.9.1 has a behavioral change from 0.9.0)
Run cargo update.2025-04-29T21:35:34ZWesley Aptekar-Casselsme@wesleyac.com2025-04-29T17:30:17Zurn:sha1:54e3933f577548f10e01ae9e979ffb110481f9b4
I updated everything except rand, because the new version of rand
interacts with #1903, thus requiring more care.
dirmgr: Backend support for cacheing protocol status.2025-04-16T23:06:51ZNick Mathewsonnickm@torproject.org2025-04-03T12:47:41Zurn:sha1:b483b454669b8b0ce93ea52896992d9234e4779d
We want to store this separately from the consensus,
because we want to access it very early in our load-from-cache
process, without checking the consensus that contains it
for timeliness.
New functions to report supported subprotocols2025-04-16T23:06:51ZNick Mathewsonnickm@torproject.org2025-04-02T18:00:00Zurn:sha1:efe36d15de88ec5b7f39db99f9d2a58e4e5db7ac
Part of #1849.
Note that these functions are distributed across crates,
so that if (in the future) we stop doing API breaks
with every release, we will get the right outputs.
Note also that these functions build the list of protocols
out of specific symbolic features, rather than numbers:
this makes it easier to avoid errors about "which feature was
Relay=4 again", and easier to avoid accidentally referring to a
protocol that doesn't exist, like "Consensus" (should be "Cons")
or "HsDir" (case is wrong).