mirrors/arti.git/crates/tor-circmgr, branch arti-v1.1.12mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.122024-01-09T13:17:45ZFollowup minor version bumps.2024-01-09T13:17:45ZNick Mathewsonnickm@torproject.org2024-01-09T13:17:45Zurn:sha1:8e883e2b00d717985746c2402bc6ee394cfd3fdf
These crates had no changes previously, but they depend on crates
that had breaking changes themselves.
tor-linkspec
tor-hspow
Patchlevel version bumps in preparation for 1.1.12.2024-01-09T13:11:17ZNick Mathewsonnickm@torproject.org2024-01-09T13:07:43Zurn:sha1:ef150707800e7aba78948f0b5dc5a2dcefaf62b6
This crate doesn't have a meaningful public API, so it just gets a patchlevel bump:
arti
These crates had nonbreaking changes, and get a patchlevel bump:
tor-rtcompat
fs-mistrust
tor-llcrypto
tor-cert
Breaking version bumps in preparation for 1.1.12.2024-01-09T13:07:43ZNick Mathewsonnickm@torproject.org2024-01-09T13:07:43Zurn:sha1:565b44dc8e0a40d82b2eb32869b04b807b19cd9c
These crates have breaking changes on their own:
tor-error
tor-netdoc
tor-dirmgr
tor-keymgr
Because of the breaking change in tor-error, and the fact that
basically every crate publicly depends on tor-error (by implementing
ErrorKind), we need to call this a breaking change on all of the
following:
tor-config
tor-geoip
tor-rtmock
tor-log-ratelim
tor-rpcbase
tor-bytes
tor-hscrypto
tor-socksproto
tor-cell
tor-proto
tor-netdoc
tor-netdir
tor-persist
tor-chanmgr
tor-ptmgr
tor-guardmgr
tor-circmgr
tor-dirclient
tor-dirmgr
tor-keymgr
tor-hsclient
tor-hsservice
tor-hsrproxy
arti-client
arti-rpcserver
arti-config
arti-hyper
arti-testing
Run "fixup-features" in preparation for release.2024-01-08T18:30:34ZNick Mathewsonnickm@torproject.org2024-01-08T18:30:34Zurn:sha1:41782552e9602390cd6fbf79374dd4e2218ea119circmgr:Resolve a warning when building without ntor-v32023-12-13T13:37:14ZNick Mathewsonnickm@torproject.org2023-12-13T13:37:14Zurn:sha1:0c0bbb7661f572d4842f1ec47ebbf66524da1cb8Fix a clippy lint2023-12-12T11:49:34ZIan Jacksonijackson@chiark.greenend.org.uk2023-12-12T11:49:34Zurn:sha1:f9631026a783fbcf5705a38aac7a33f0261f9037
warning: consider adding a `;` to the last statement for consistent formatting
--> crates/tor-circmgr/src/build.rs:162:13
|
162 | handshake_res = circ.create_firsthop_ntor(ct, params).await
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: add a `;` here: `handshake_res = circ.create_firsthop_ntor(ct, params).await;`
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#semicolon_if_nothing_returned
ClientCir: use ntor_v3 handshake when target supports it2023-12-07T15:54:46ZJim Newsomejnewsome@torproject.org2023-11-27T19:37:51Zurn:sha1:777cd7d8461c143f8bfbe40b7a26522bdb2742fdtor-circmgr: add experimental feature "ntor_v3"2023-12-07T15:45:49ZJim Newsomejnewsome@torproject.org2023-11-27T18:59:57Zurn:sha1:ea470447efdb6e2dd0d1bb857f516684a0fc1f07Two more patchlevel bumps2023-12-04T16:37:56ZNick Mathewsonnickm@torproject.org2023-12-04T16:37:56Zurn:sha1:c730cd00e5c131f62425be190579c7ce4748e11c
These crates both depend on tor-error. Since tor-error got a
patchlevel bump, they now depend on the new version, which means by
our rules that _they_ get a patchlevel bump themselves.
tor-geoip
tor-rpcbase
Bump minor versions in preparation for release2023-12-04T16:35:23ZNick Mathewsonnickm@torproject.org2023-12-04T16:22:58Zurn:sha1:fba95e4b4708929ed09554632acd2e9f15e3c086
This crate is new, and gets a bump to 0.1.0.
tor-log-ratelim
This crate had a breaking change:
tor-persist
tor-llcrypto had a breaking change. These crates _are_
tor-llcrypto, or (transitively) depend on it. I am assuming that
they all re-expose something from it in a way that matters:
tor-llcrypto
tor-bytes
tor-hscrypto
tor-socksproto
tor-checkable
tor-cert
tor-linkspec
tor-cell
tor-proto
tor-netdoc
tor-consdiff
tor-netdir
tor-chanmgr
tor-ptmgr
tor-guardmgr
tor-circmgr
tor-dirclient
tor-dirmgr
tor-keymgr
tor-hsclient
tor-hsservice
tor-hsrproxy
arti-client
arti-rpcserver
arti-hyper