mirrors/arti.git/crates/tor-proto, branch arti-v1.1.6

Bump patchlevel versions on crates with smaller changes

2023-06-30T12:42:21Z

Done with the commands below. The following crates have had various changes, and should get a patchlevel bump. Since they are pre-1.0, we do not need to distinguish new APIs from other changes. ``` cargo set-version --bump patch -p arti-client cargo set-version --bump patch -p safelog cargo set-version --bump patch -p tor-bytes cargo set-version --bump patch -p tor-cert cargo set-version --bump patch -p tor-circmgr cargo set-version --bump patch -p tor-config cargo set-version --bump patch -p tor-consdiff cargo set-version --bump patch -p tor-dirclient cargo set-version --bump patch -p tor-dirmgr cargo set-version --bump patch -p tor-error cargo set-version --bump patch -p tor-hsservice cargo set-version --bump patch -p tor-linkspec cargo set-version --bump patch -p tor-llcrypto cargo set-version --bump patch -p tor-netdir cargo set-version --bump patch -p tor-netdoc cargo set-version --bump patch -p tor-proto cargo set-version --bump patch -p tor-rpcbase cargo set-version --bump patch -p tor-socksproto ``` This crate has new features, but no new non-experimental Rust APIs. So even though it is post-1.0, it gets a patchlevel bump. ``` cargo set-version --bump patch -p arti ```

Bump minor versions on crates with breaking changes

2023-06-30T12:38:16Z

Done with: ``` cargo set-version --bump minor -p tor-hsclient cargo set-version --bump minor -p arti-rpcserver cargo set-version --bump minor -p tor-hscrypto cargo set-version --bump minor -p tor-cell ```

Resolve XXXs from fixup-features.

2023-06-29T21:14:00Z

Some of these seem spurious: it looks like fixup-features resolved an issue and then complained about it too. I'll investigate further.

Run "fixup-features".

2023-06-29T21:09:52Z

Mark all {hs,onion-serivce}-client features as non-experimental.

2023-06-29T17:09:37Z

proto: ClientCirc: remove now-obsolete note on Clone-ness

2023-06-28T19:26:22Z

proto: document ClientCirc lifecycle better.

2023-06-28T19:26:22Z

proto: document channel lifecycle better.

2023-06-28T19:26:22Z

Merge branch 'ticket_914' into 'main'

2023-06-28T10:54:05Z

Remove support for receiving unauthenticated SENDMEs. Closes #914 See merge request tpo/core/arti!1283

Back down x25519-dalek to 2.0.0-pre.1 from 2.0.0-rc.2

2023-06-27T17:55:24Z

========================= Notes from nickm: (This differs from pinkforest's original MR: It removes the Cargo.lock changes and the version bump on tor-llcrypto.) Minimal Cargo.lock changes from downgrade. (These are exactly those changes generated by running "build" and "test".) There are several reasons to do this: * It's best to bump all of our dalek dependencies at once to rc.3 or later, rather than the piecemeal approach we've been stuck with so far. * We don't want to do this bump right now, since there are some tricky questions about clamping we need to figure out (see #808), and we need to make sure we get them right, and we're in a distracted this week. * We _do_ need to move away from 2.0.0-rc.2 right now, since it was causing a failure in `cargo install arti`, and then it got yanked. Thanks to pinkforest for helping us out here and explaining all of this! Fixes #926. Commit-edited-by: Nick Mathewson