mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.3 2023-03-31T12:30:14Z 2023-03-31T12:30:14Z Nick Mathewson nickm@torproject.org 2023-03-31T12:30:14Z urn:sha1:9ef115a7fb21fe7267d1d91ba7babac8e1b7542e These crates had no changes until just a moment ago. But since we updated the versions on some of their dependents, they have now changed themselves. Thus they get patchlevel bumps. ``` tor-rtmock tor-protover tor-socksproto tor-consdiff tor-chanmgr tor-dirclient tor-hsservice ``` 2023-03-31T12:28:06Z Nick Mathewson nickm@torproject.org 2023-03-31T12:28:06Z urn:sha1:e208fb15adb800ae41e472db464f984e9f4a4f5c These crates have had breaking changes. They are pre-1.0, so they get a minor bump. ``` tor-basic-utils tor-config ``` 2023-03-31T12:24:39Z Nick Mathewson nickm@torproject.org 2023-03-31T12:24:39Z urn:sha1:a81ab391ae9cc3b48cf08cf1b911f1b4cfa8be76 For these crates, the changes are nontrivial, so we _do_ bump the versions on which their dependent crates depend. Fortunately, since they are all pre-1.0, we don't need to distinguish semver-additions from other changes. (Except for arti, which _is_ post-1.0, but gets a patchlevel bump anyway.) These are unstable crates with breaking changes: ``` tor-hscrypto tor-hsclient ``` These have new or extended APIs: ``` safelog tor-bytes tor-cell tor-linkspec tor-llcrypto tor-proto tor-cert arti-client ``` These have new unstable APIs or features: ``` tor-netdoc tor-circmgr (also broke some unstable APIs) arti (is post-1.0) ``` These have bugfixes only: ``` caret tor-dirmgr ``` 2023-03-30T12:33:44Z Nick Mathewson nickm@torproject.org 2023-03-30T12:33:44Z urn:sha1:26ee1feeb1c4f528cfb60e954c690158f838794a 2023-03-21T13:08:14Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-03-21T12:10:44Z urn:sha1:d24a47c1d9b3793b8f2b0f456c17b013724d6e50 2023-03-10T12:09:50Z Nick Mathewson nickm@torproject.org 2023-03-10T12:03:23Z urn:sha1:552acbf07fac3c3c9c431caeea128c903b0bf557 Apparently 1.68 now warns when you call into_iter() on something that's already an iterator. Fair enough. Let's stop doing that. 2023-03-08T12:08:17Z Nick Mathewson nickm@torproject.org 2023-03-08T12:08:17Z urn:sha1:ac5469d0b6eeecd3fe73d561f7f0602f67749796 Doing this means that any attempt to use a read-only store would crash as soon as it found that the consensus was usable. It seems that this bug was introduced at some point doing all the dirmgr refactors we did over the past year. Perhaps there should be a test for running with a read-only store. Fixes #779 2023-02-28T12:18:37Z Nick Mathewson nickm@torproject.org 2023-02-28T12:18:37Z urn:sha1:2c9f8e35479fb2b59bb51de3efb424b0b1df4a56 These crates didn't have any changes until now, when I bumped the versions of some other crates they depend on: tor-consdiff arti-hyper arti-bench arti-testing 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-28T12:05:15Z Nick Mathewson nickm@torproject.org 2023-02-28T12:05:15Z urn:sha1:3e257a7cb57801329f013e7c1dc2d8c2dc598e47 This includes tor-cell, tor-proto, and tor-netdir.