mirrors/arti.git/crates/tor-hsclient, branch arti-v1.4.3mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.4.32025-05-01T16:22:28Zrelease: 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.
Include "bug" in all bug error messages2025-04-28T14:06:57ZNick Mathewsonnickm@torproject.org2025-04-28T14:06:57Zurn:sha1:aa813e37c94898ed621eb259b67754f1e70a67bbprotover, *: Add documentation about what "supported" means.2025-04-16T23:06:51ZNick Mathewsonnickm@torproject.org2025-04-14T00:42:31Zurn:sha1:11148719ba04aab37c7784d198018eeacced69c2Add warnings about removing supported protocols.2025-04-16T23:06:51ZNick Mathewsonnickm@torproject.org2025-04-07T15:27:42Zurn:sha1:ba612260ae603c8e5eba37206c21fd089afe075dNew 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).
fix `clippy::unneeded_struct_pattern`2025-04-03T17:32:58ZSteven Engleropara@torproject.org2025-04-03T17:30:13Zurn:sha1:5395b385584599ee6a0f8fc005ded81910d60f4b
Example:
```text
warning: struct pattern is not needed for a unit variant
--> crates/hashx/src/program.rs:165:32
|
165 | Instruction::Target { .. } => Opcode::Target,
| ^^^^^^^ help: remove the struct pattern
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#unneeded_struct_pattern
note: the lint level is defined here
--> crates/hashx/src/lib.rs:9:9
|
9 | #![warn(clippy::all)]
| ^^^^^^^^^^^
= note: `#[warn(clippy::unneeded_struct_pattern)]` implied by `#[warn(clippy::all)]`
```
Bump all the unstable tor- and arti- crates to 0.29.0.2025-03-31T17:59:51ZGabriela Moldovangabi@torproject.org2025-03-31T17:34:50Zurn:sha1:1be579f99a7c0784bd7710f9ee6ee9a6b10c85df
Done using:
```
for crate in $(./maint/list_crates | rg '^(tor|arti-)'); do
cargo set-version -p $crate 0.29.0
done
```