mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.6 2023-06-30T12:42:21Z 2023-06-30T12:42:21Z Nick Mathewson nickm@torproject.org 2023-06-30T12:42:21Z urn:sha1:de13a7319b7de5a336a70f128d1904954ed77f82 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 ``` 2023-06-30T12:38:16Z Nick Mathewson nickm@torproject.org 2023-06-30T12:38:16Z urn:sha1:65e81bf0ca876669a15943caf4cf388515366623 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 ``` 2023-06-29T17:09:37Z Nick Mathewson nickm@torproject.org 2023-06-29T17:09:37Z urn:sha1:d164a9dac216536bf960c7cb6a1f43d25ca55dc6 2023-06-28T12:32:54Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-06-23T15:58:08Z urn:sha1:cdad2db082afd38bfccf31ce69248ed8c4956369 I think these should go in `[circuit_timing]`. That section already has some retry parameters, so is not strictly *timing*. This is not honoured yet. 2023-06-26T13:30:54Z Nick Mathewson nickm@torproject.org 2023-06-26T13:30:54Z urn:sha1:0bffdf23a4c9f185b88eb426681bf9ca5f12610f The breaking changes here do not seem to affect us. 2023-06-12T17:15:59Z Nick Mathewson nickm@torproject.org 2023-06-12T17:12:34Z urn:sha1:ac90cb7500f2f1086247004972e65c51ca973fde We need the fix from [82d69902], which first appeared in async-trait version 1.54. (Technically we only need this fix in tor-hsclient, but we may as well update our minimal async-trait version everywhere.) [82d69902]: https://github.com/dtolnay/async-trait/commit/82d69902535f5cb7f5d9e1ea4168c64abd496389 2023-06-01T14:03:05Z Nick Mathewson nickm@torproject.org 2023-06-01T14:03:05Z urn:sha1:daf5ecc15340c5910fdb912ea9099719befd916e Generated with the following commands: ``` cargo set-version --bump minor -p tor-cell cargo set-version --bump minor -p tor-linkspec cargo set-version --bump minor -p tor-proto cargo set-version --bump minor -p tor-netdoc cargo set-version --bump minor -p tor-circmgr cargo set-version --bump patch -p tor-cert cargo set-version --bump patch -p tor-basic-utils cargo set-version --bump patch -p tor-rpcbase cargo set-version --bump patch -p tor-llcrypto cargo set-version --bump patch -p tor-hscrypto cargo set-version --bump patch -p tor-checkable cargo set-version --bump patch -p tor-async-utils cargo set-version --bump patch -p caret cargo set-version --bump patch -p fs-mistrust cargo set-version --bump patch -p safelog cargo set-version --bump patch -p retry-error cargo set-version --bump patch -p tor-error cargo set-version --bump patch -p tor-config cargo set-version --bump patch -p tor-events cargo set-version --bump patch -p tor-units cargo set-version --bump patch -p tor-rtcompat cargo set-version --bump patch -p tor-rtmock cargo set-version --bump patch -p tor-protover cargo set-version --bump patch -p tor-bytes cargo set-version --bump patch -p tor-socksproto cargo set-version --bump patch -p tor-consdiff cargo set-version --bump patch -p tor-netdir cargo set-version --bump patch -p tor-congestion cargo set-version --bump patch -p tor-persist cargo set-version --bump patch -p tor-chanmgr cargo set-version --bump patch -p tor-ptmgr cargo set-version --bump patch -p tor-guardmgr cargo set-version --bump patch -p tor-dirclient cargo set-version --bump patch -p tor-dirmgr cargo set-version --bump patch -p tor-hsclient cargo set-version --bump patch -p tor-hsservice cargo set-version --bump patch -p arti-client cargo set-version --bump patch -p arti-rpcserver cargo set-version --bump patch -p arti-config cargo set-version --bump patch -p arti-hyper cargo set-version --bump patch -p arti cargo set-version --bump patch -p arti-bench cargo set-version --bump patch -p arti-testing ``` 2023-05-15T15:00:28Z Nick Mathewson nickm@torproject.org 2023-05-15T15:00:28Z urn:sha1:6fa821238dcaa98f08d3b0a92af7e1f9843296dd 2023-05-15T14:41:32Z Nick Mathewson nickm@torproject.org 2023-05-15T12:37:35Z urn:sha1:4b08ef76a0e9d913ea2c2e7ab0cda48ee2eba805 This litters our Cargo.toml files with "XXX" entries that we should fix. 2023-05-15T13:09:43Z Nick Mathewson nickm@torproject.org 2023-05-15T12:34:47Z urn:sha1:e2e125fef7c027a24f23397eb1644a8565ad5d8b