mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.2 2023-02-28T12:13:27Z 2023-02-28T12:13:27Z Nick Mathewson nickm@torproject.org 2023-02-28T12:13:27Z urn:sha1:f41449d0bd9a2db5f72dd9941fb897e5cd9b922d These crates have had small code changes, but no API additions: tor-config tor-socksproto tor-cert tor-chanmgr tor-ptmgr tor-guardmgr tor-circmgr tor-dirclient tor-dirmgr arti tor-hsservice tor-congestion These crates have had API extensions: fs-mistrust tor-llcrypto tor-bytes tor-checkable tor-linkspec tor-netdoc tor-persist arti-client 2023-02-01T15:36:29Z Nick Mathewson nickm@torproject.org 2023-02-01T15:36:29Z urn:sha1:7c1b6a5a81e382be6210c7e2b0aae9695ad0bef4 These crates had API or behavior changes that may affect downstream crates. Fortunately, they're all version 0.x, and don't need minor bumps for this. 2023-02-01T15:23:58Z Nick Mathewson nickm@torproject.org 2023-02-01T15:23:58Z urn:sha1:66f594a4b6fac81137886be90a7bda3687923d48 These changes influence behavior, but not effect compatibility. (If I messed up, and any crate except for `arti` has non-breaking API changes, that's still fine, since they are all version 0.x.) 2022-11-30T20:10:16Z Nick Mathewson nickm@torproject.org 2022-11-30T20:10:16Z urn:sha1:38bef96b99dbf17922dc601d4250abc0368b519f We made this job easy this time around: by incrementing our MSRV, we have forced ourselves to do at least a minor bump everywhere. 2022-11-10T15:57:33Z Nick Mathewson nickm@torproject.org 2022-11-07T19:18:02Z urn:sha1:936920b26e43447a010e249a9b5a5b9f69ca0da1 2022-11-03T11:37:23Z Ian Jackson ijackson@chiark.greenend.org.uk 2022-11-01T10:59:37Z urn:sha1:48f48841e1aa99f0c76c2078812b003ec191540a 0.99.[012] have a bug https://github.com/JelteF/derive_more/issues/114 which makes the Deref derive for bridgedesc::StateGuard not work and therefore breaks minimal-versions CI. It seems simpler to require the newer version everywhere. 2022-09-01T12:59:49Z Nick Mathewson nickm@torproject.org 2022-09-01T12:52:51Z urn:sha1:96875ea20875e3a5cfc9f348365f19a158578190 Because we want to work more on ensuring that our semver stability story is solid, we are _not_ bumping arti-client to 1.0.0 right now. Here are the bumps we _are_ doing. Crates with "minor" bumps have had API breaks; crates with "patch" bumps have had new APIs added. Note that `tor-congestion` is not bumped here: it's a new crate, and hasn't been published before. ``` tor-basic-utils minor fs-mistrust minor tor-config minor tor-rtcompat minor tor-rtmock minor tor-llcrypto patch tor-bytes patch tor-linkspec minor tor-cell minor tor-proto minor tor-netdoc patch tor-netdir minor tor-persist patch tor-chanmgr minor tor-guardmgr minor tor-circmgr minor tor-dirmgr minor arti-client minor arti-hyper minor arti major arti-bench minor arti-testing minor ``` 2022-08-24T16:22:41Z trinity-1686a trinity@deuxfleurs.fr 2022-08-17T19:13:13Z urn:sha1:7f939fa4804b3c934343141b79e8e2ded5fe0b0d 2022-08-01T13:43:09Z Nick Mathewson nickm@torproject.org 2022-08-01T13:43:09Z urn:sha1:f5dcb98f06761cdd8660e12853074204649a5b2f Done with these commands: ``` cargo set-version -p fs-mistrust --bump minor cargo set-version -p tor-bytes --bump minor cargo set-version -p tor-socksproto --bump minor cargo set-version -p tor-cert --bump minor cargo set-version -p tor-linkspec --bump minor cargo set-version -p tor-cell --bump minor cargo set-version -p tor-netdir --bump minor cargo set-version -p tor-persist --bump minor cargo set-version -p tor-chanmgr --bump minor cargo set-version -p tor-guardmgr --bump minor cargo set-version -p tor-circmgr --bump minor cargo set-version -p tor-dirclient --bump minor cargo set-version -p tor-dirmgr --bump minor cargo set-version -p arti-client --bump minor cargo set-version -p arti --bump minor ``` 2022-07-06T15:47:17Z Nick Mathewson nickm@torproject.org 2022-07-05T14:28:18Z urn:sha1:853aed685983a83e97c273f2135d23f09ff2bef0 Every error now has an action (what we were trying to do), a resource (what we were trying to do it to), and a source (what problem we encountered). Initially I tried to add "action" and "resource" fields to error variants individually, but that led to a combinatorial explosion. Part of #323.