proto: Update semver with the changes to the logging

2026-08-03T18:27:50Z

Signed-off-by: David Goulet

proto: Pass the allowed incoming commands to CreateRequestHandler

2026-06-30T17:40:25Z

This enables us to make these configurable: any relays that are not configured to be an exit will exclude BEGIN and RESOLVE from their list of allowed commands, causing exit and DNS streams to be rejected as soon as the BEGIN/RESOLVE cell is received in the circuit reactor. Context: https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/4145#note_3430345 Part of #2606

Remove semver.md files

2026-06-30T16:59:48Z

proto: Pass an IncomingStreamRequestFilter factory to the create handler

2026-06-29T13:52:56Z

This implements what we discussed in `doc/dev/notes/relay-streams.md` (lines 218-234): > Currently, to allow incoming stream requests on a circuit, > you first need to call `RelayCirc::allow_stream_requests()` > to install a `CmdChecker` and `IncomingStreamRequestFilter`. > This is not ideal, because `allow_stream_requests()` will need to be > called unconditionally, on each `RelayCirc`, > right after it's created in the `CreateHandler` impl > (which in turn, would mean making `handle_create()` async too, > because `allow_stream_requests()` is async, which wouldn't be great). > > So, the first step here is to rework the `RelayCirc` API to make relay circuits > be constructable with a list of allowed `RelayCmd`s and `IncomingStreamRequestFilter` > from the get-go ([#2582]), and to get rid of `allow_stream_requests()`, > which will enable the `CREATE*` handler to remain non-`async`. > > In any case, the `CREATE*` handler will still require some changes, > because it needs to be initialized with an `IncomingStreamRequestFilter`, I am not sure using an `IncomingStreamRequestFilter` "factory" is necessarily the right approach here, but the circuit `Reactor`'s constructor needs to take an `IncomingStreamRequestFilter`, and `IncomingStreamRequestFilter` is not `Clone` (and FWIW, I think it's better if we don't make it `Clone`). One obvious limitation is that the `IncomingStreamRequestFilter` of the circuit reactor is fixed for the entire lifetime of the circuit. In practice, I don't think this is going to be a problem, because the arti-relay `IncomingStreamRequestFilter` is only going be used for * preventing single-hop exit streams * per-circuit rate-limiting. Both of these checks will require the filter to have access to a recent `NetDir`, which is straightforward if the filter has an Arc (as mentioned in doc/dev/notes/relay-streams.md, `NetDirProvider` has a handy non-async `timely_netdir()` function we can use). And since these checks are based on consensus params, we don't really need to ever update an already-built circuit with a new `IncomingStreamRequestFilter` (because all `IncomingStreamRequestFilter` will have the ability to obtain a fresh `NetDir` as needed). Nevertheless, I left a TODO about this, because I expect this type to change once we figure out all the other pieces needed for #1448.

proto: Add crate-level exports for two extra stream types (fmt)

2026-06-17T13:38:44Z

Remove semver.md files post-release

2026-06-01T18:24:24Z

tor-proto: clean up `CIRCUIT_BUFFER_SIZE`

2026-05-21T16:35:59Z

Remove semver.md files post-release

2026-03-03T12:29:50Z

proto: Remove unused ChannelBuilder

2026-02-19T20:57:29Z

Signed-off-by: David Goulet

proto: Rename CircSyncView to CircHopSyncView

2026-02-16T15:24:51Z

And update the docs

mirrors/arti.git/crates/tor-proto/semver.md, branch arti-v2.5.1

proto: Update semver with the changes to the logging

proto: Pass the allowed incoming commands to CreateRequestHandler

Remove semver.md files

proto: Pass an IncomingStreamRequestFilter factory to the create handler

proto: Add crate-level exports for two extra stream types (fmt)

Remove semver.md files post-release

tor-proto: clean up `CIRCUIT_BUFFER_SIZE`

Remove semver.md files post-release

proto: Remove unused ChannelBuilder

proto: Rename CircSyncView to CircHopSyncView