mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.12 2024-01-09T13:20:24Z 2024-01-09T13:20:24Z Nick Mathewson nickm@torproject.org 2024-01-09T13:20:24Z urn:sha1:00e49794591b5be7a16195d9a104b39444ccfd1b 2024-01-09T13:17:45Z Nick Mathewson nickm@torproject.org 2024-01-09T13:17:45Z urn:sha1:8e883e2b00d717985746c2402bc6ee394cfd3fdf These crates had no changes previously, but they depend on crates that had breaking changes themselves. tor-linkspec tor-hspow 2024-01-09T13:11:17Z Nick Mathewson nickm@torproject.org 2024-01-09T13:07:43Z urn: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 2024-01-09T13:07:43Z Nick Mathewson nickm@torproject.org 2024-01-09T13:07:43Z urn: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 2024-01-02T13:56:50Z Ian Jackson ijackson@chiark.greenend.org.uk 2024-01-02T13:13:34Z urn:sha1:6e473865396e095e154bbd1b8ae63c72d1b91339 clippy in current stable thinks |(a, b)| (a, b) is always the identity function, but due to match ergonomics, it might be an implicit copy. This is fixed in nightly by https://github.com/rust-lang/rust-clippy/pull/11792 2023-12-04T16:37:56Z Nick Mathewson nickm@torproject.org 2023-12-04T16:37:56Z urn: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 2023-12-04T16:35:23Z Nick Mathewson nickm@torproject.org 2023-12-04T16:22:58Z urn: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 2023-12-04T16:33:36Z Nick Mathewson nickm@torproject.org 2023-12-04T16:22:58Z urn:sha1:606905bd1fa3307a77a02463fa863f4c2b7cb890 These crates had backward-compatible changes, and get a patchlevel bump only: fs-mistrust tor-error tor-config tor-rtcompat tor-rtmock This crate exposes no non-CLI APIs, and gets a patchlevel bump only: arti 2023-11-28T16:35:51Z Nick Mathewson nickm@torproject.org 2023-11-28T16:35:51Z urn:sha1:1b53c4ca3059fc395c98e2e6d0eb3b58f37c8ec1 2023-11-20T15:24:09Z Nick Mathewson nickm@torproject.org 2023-11-15T22:54:34Z urn:sha1:4b1eef41ee8113b6c4b3d418240dc4c23ea31a50 It does not help that C tor has a set of parameters and a set of configuration options with exactly the same names which configure the same thing in two slightly different ways.