mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.3 2023-03-31T13:14:35Z 2023-03-31T13:14:35Z Nick Mathewson nickm@torproject.org 2023-03-31T13:14:35Z urn:sha1:d3a727a5a124ffe80a32058a5a297eaa75e57af6 It is now a (conditional, experimental) dependency of arti-client. 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-30T19:12:57Z Nick Mathewson nickm@torproject.org 2023-03-30T19:12:57Z urn:sha1:f245fc12bb2b89f21bf88c6d667bd2592b8c95af 2023-03-30T14:58:47Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-03-30T14:56:29Z urn:sha1:23c7bd9174c454c5eb9ba83c8d580384434c1baa Apply this churn, which I deferred for ease of review. 2023-03-30T14:49:07Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-03-30T10:32:38Z urn:sha1:3ed9dca842bc673c947258c201c5adce684899bb The old name was unwieldy and other crates can just as well name it by the crate scope. 2023-03-30T14:49:07Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-03-28T16:32:37Z urn:sha1:926abf3ade85776e73e32b9d803febc5b1326453 This will be more convenient inside tor-hsclient. In arti-client, this mirrors the way TorClient::get_or_launch_exit_circ works. 2023-03-28T14:49:45Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-03-28T14:24:33Z urn:sha1:5ff24c9f844640c36b2c6931da07b35ba8a97f67 Obviously it will need this! 2023-03-28T14:49:45Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-03-28T11:18:06Z urn:sha1:9b6be7eaa77f16be33cdebc75e6a68ee67a913b1 We separated this out in the circmgr API. This is what the HS client needs. It doesn't want to participate in the general circuit pool.