mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.7 2023-08-01T14:57:55Z 2023-08-01T14:57:55Z Nick Mathewson nickm@torproject.org 2023-08-01T14:57:55Z urn:sha1:3acdf102c705314aec63679e97240bb7d981d1c8 These crates are at version 0.x.y, so we don't need to distinguish new-feature changes from other changes: ``` tor-basic-utils fs-mistrust tor-error tor-geoip tor-checkable tor-linkspec tor-netdoc tor-netdir tor-persist tor-ptmgr tor-hsservice ``` This crate has a breaking change, but only when the semver-breaking feature `experimental-api` is enabled: ``` tor-config ``` This crate is at version 1.x.y, but has no new public APIs, and therefore does not need a minor version bump: ``` arti ``` 2023-07-22T07:10:34Z Dimitris Apostolou dimitris.apostolou@icloud.com 2023-07-22T07:10:34Z urn:sha1:947ddfff0cfac3fef0e3d7ebc14182c638a1d90b 2023-07-11T09:53:09Z Nick Mathewson nickm@torproject.org 2023-07-11T09:53:09Z urn:sha1:bcf574cef5f8eb0005a828722b64baa4268ad427 Explain the code for the #952 fix. See merge request tpo/core/arti!1391 2023-07-10T12:49:51Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-07-10T11:19:32Z urn:sha1:473447a82e099fd52a674c28f5bc24b3e05208c0 2023-07-10T12:00:08Z Nick Mathewson nickm@torproject.org 2023-07-07T19:50:56Z urn:sha1:c2601ec8967cff4dbd1b745b970552dcd36e72de Let's explain what Trinity did in its fix for #952, so that we know why this code is here the next time we find it. 2023-07-07T19:06:05Z trinity-1686a trinity@deuxfleurs.fr 2023-07-07T19:06:05Z urn:sha1:2d170425c053b1a00fedb80fc5de78dce2ea8d64 2023-07-06T18:32:23Z Nick Mathewson nickm@torproject.org 2023-07-06T18:32:23Z urn:sha1:03f9f9987a7ba42368d82363bef7f569e32ffe2c Closes #950. 2023-06-30T14:28:53Z Nick Mathewson nickm@torproject.org 2023-06-30T14:28:53Z urn:sha1:27bd990a79b14e27cebf3e64b425457901a7af91 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 ```