mirrors/arti.git/crates/arti-relay, branch arti-v2.4.0

Bump all the unstable tor- and arti- crates to 0.43.0

2026-06-01T16:32:03Z

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

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

2026-06-01T16:30:04Z

The non-{arti-,tor-} crates are: ``` ./maint/list-crates | rg -v '^(tor|arti)' oneshot-fused-workaround web-time-compat slotmap-careful test-temp-dir fslock-guard hashx equix caret fs-mistrust safelog retry-error futures-copy ``` We split them in the following categories: * crates with no changes (no version bumps): ``` oneshot-fused-workaround: No change. web-time-compat: No change. slotmap-careful: No change. test-temp-dir: No change. caret: No change. safelog: No change. retry-error: No change. futures-copy: No change. ``` Obtained with: ``` 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, but not the dependend-on version): - equix * crates where functional changes were made, but no APIs were broken (bump patch): - fs-mistrust * crates where APIs were broken (bump minor): - hashx - fslock-guard The bumps from this commit were created using this script: ``` PATCH_NF=( equix ) PATCH=" fs-mistrust " MINOR=" hashx fslock-guard " ./maint/bump-nodep "${PATCH_NF[@]}" for crate in $PATCH; do cargo set-version --bump patch -p $crate; done for crate in $MINOR; do cargo set-version --bump minor -p $crate; done ```

arti-relay: Make the metrics feature non-experimental

2026-06-01T09:19:01Z

`maint/fixup-features` was complaining that `metrics` was reachable from `full` and also `__is_experimental`. I'm making `metrics` a non-experimental feature, because the whole of `arti-relay` is experimental (so there is really no need mark any of its individual features as experimental right now).

relay: Remove docs type link that are outside scope

2026-05-28T16:11:56Z

Signed-off-by: David Goulet

relay: Recompute valid_until cache in view constructor

2026-05-28T16:11:56Z

The recompute of the valid_until cache is done now in the constructor of FullKeyView so the view is directly usable once built. Else, the caller always need to call the recompute function which is error prone especially when used as a throwaway view. Also, without this change, building the view and then attempting to log the public keys would fail. Signed-off-by: David Goulet

relay: Introduce src/task/crypto/keys.rs

2026-05-28T16:11:56Z

Move all key related action function to keys.rs in order to alleviate crypto.rs. The Reactor will get more functionnalities soon so cleanup. No behavior change, just code movement. Related to #2548

relay: Rename try_rotate_keys_no_lock()

2026-05-28T16:11:56Z

Remove the _no_lock() since no more locks now. Signed-off-by: David Goulet

relay: Make FullKeyView pub(super)

2026-05-28T16:11:56Z

Now, the FullKeyView is officially only seen by the crypto task. Signed-off-by: David Goulet

relay: Remove locking of FullKeyView

2026-05-28T16:11:56Z

No need for the valid_until cache locking that used to ensure coherent view accross tasks. As we move towards having the FullKeyView be solely owned by the crypto task, no need for locking. Future commit will introduce a control command channel which will be used to get keys for other tasks. The valid_until cache is kept though because it helps with key lookups to avoid walking all keys each time. Signed-off-by: David Goulet

relay: Rename try_generate_keys()

2026-05-28T16:11:56Z

Rename it to init_keys() so it capture the semantic of initialization especially that now it returns a InitKeyMaterial. This is so we don't use this function outside initialization in the future. Signed-off-by: David Goulet