mirrors/arti.git/crates/tor-hsservice, 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 ```

Bump the versions of the non-{arti-,tor-} crates.

2025-07-07T17:41:41Z

The non-{arti-,tor-} crates are: ``` ./maint/list_crates | rg -v '^(tor|arti)' oneshot-fused-workaround slotmap-careful test-temp-dir fslock-guard hashx equix caret fs-mistrust safelog retry-error ``` We split them in the following categories: * crates with no changes (no version bumps): None ``` maint/changed_crates -v "arti-v$LAST_VERSION" 2>&1 >/dev/null | grep -i "no change" | grep -v '$tor\|arti$-' ``` * crates that only have non-functional changes (bump the patch version): - oneshot-fused-workaround - slotmap-careful - test-temp-dir - fslock-guard - hashx - equix - caret - safelog - retry-error * crates where APIs were broken (bump minor): - fs-mistrust (the implicit once_cell feature was removed) The bumps from this commit were created using this script: ``` PATCH=" oneshot-fused-workaround slotmap-careful test-temp-dir fslock-guard hashx equix caret safelog retry-error " for crate in $PATCH; do cargo set-version --bump patch -p $crate; done MINOR=" fs-mistrust " for crate in $MINOR; do cargo set-version --bump minor -p $crate; done ```

tor-hsservice: Suppress false-positive clippy::useless_concat.

2025-07-07T16:03:11Z

Temporarily suppress mismatched_lifetime_syntaxes.

2025-07-07T15:50:04Z

See #2060.

Merge branch 'arti-1.4.5-prep' into 'main'

2025-07-07T13:26:54Z

Run fixup-features, upgrade deps in preparation for release See merge request tpo/core/arti!3083

Upgrade to derive-deftly 1.1.0.

2025-07-07T11:01:51Z

I had to also bump `toml` to `0.8.23`, because `toml 0.8.22` is incompatible with `serde_spanned 0.6.9` (which is automatically pulled in because of the d-d upgrade).

hspow: Add a clippy::cognitive_complexity exception

2025-07-03T18:49:04Z

hsservice: Stop using HopNum and use TargetHop

2025-06-26T14:18:30Z

This requires some changes to the tor-proto crate to handle the inbound TargetHop from the HS subsystem and then resolve it into a HopNum for a single circuit. It is expected that this will change again with Conflux to only use HopLocation internally in a Tunnel and then use HopNum into a Circuit. Signed-off-by: David Goulet

proto: Make send_raw_msg() use a TargetHop

2025-06-26T14:18:30Z

In order for this to work, a last_target_hop() function is added to ClientCirc in order to return a precise hop location as a TargetHop of the last hop. This is needed because in the HS subsystem, we need such value in order to get a location on the last physical hop before adding the virtual hop. The RDV1 cell is sent to that last target hop while the allow_stream_request() is done on the virtual target hop. Signed-off-by: David Goulet

hs: Remove the use of HopNum and instead use TargetHop

2025-06-26T14:18:30Z

This is in the spirit of making everything going inbound the tor-proto crate to use a TargetHop. This becomes much easier for the HS subsystem as it only uses the last hop for its conversation and setup. Signed-off-by: David Goulet