mirrors/arti.git/crates/tor-dirclient, branch arti-v1.1.10 mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.10 2023-10-31T15:43:13Z Merge branch 'semver-bumps' into 'main' 2023-10-31T15:43:13Z Nick Mathewson nickm@torproject.org 2023-10-31T15:43:13Z urn:sha1:c66797dcb4518f6eb5bd045c551595b263b06b5d Update versions for today's releases. See merge request tpo/core/arti!1716 Patch version bumps in crates without breaking changes 2023-10-31T13:12:35Z Nick Mathewson nickm@torproject.org 2023-10-31T13:00:42Z urn:sha1:537d98a12eedf5604fe28183ec603dd3609bb070 ``` These crates have new APIs: tor-async-utils ADDED tor-config ADDED tor-hscrypto ADDED tor-netdoc ADDED, plus BREAKING-experimental. These crates have patch-level changes only: tor-netdir (bugfix only). (re-exposes netdoc) arti-rpcserver (tweaks only, uses nothing that broke.) arti 1.1.10, no stable public APIs. ``` Minor version bumps in crates with breaking changes. 2023-10-31T13:12:35Z Nick Mathewson nickm@torproject.org 2023-10-31T12:54:00Z urn:sha1:4460d8b3a5f801db2b20ca0e83dadd0bc8ccf5da ``` tor-basic-utils BREAKING tor-rtmock BREAKING. tor-cert BREAKING tor-cell BREAKING tor-proto BREAKING: re-exposes cell. (Also BREAKING-experimental) tor-chanmgr BREAKING: Re-exposes proto. tor-ptmgr BREAKING: re-exposes tor-chanmgr tor-guardmgr BREAKING: re-exposes proto. (Only for ClockSkew I think?) tor-circmgr BREAKING: re-exposes proto tor-dirclient BREAKING tor-hsclient BREAKING, re-exposes proto. tor-hsservice BREAKING, re-exposes proto. tor-hsrproxy BREAKING arti-client BREAKING: re-exposes proto. arti-hyper: BREAKING, re-exposes arti-client. tor-dirmgr Let's assume BREAKING, very high-level. tor-keymgr BREAKING, but experimental. ``` Add cfg_attr allow(unused_imports) to two crates 2023-10-31T11:36:45Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-10-31T11:32:08Z urn:sha1:17fd8979d50901f93824e98b1eac007715ba75aa As per this comment, and preceding discussion https://gitlab.torproject.org/tpo/core/arti/-/issues/1060#note_2959187 tor-dirclient, tor-netdoc: Add TODO SPECs. 2023-10-24T14:42:35Z Gabriela Moldovan gabi@torproject.org 2023-10-24T12:06:53Z urn:sha1:8cdcced5e612709d6c4c4ae9d27211818d4ab285 tor-dirclient: Always set the Content-Length header (fmt). 2023-10-24T14:42:35Z Gabriela Moldovan gabi@torproject.org 2023-10-24T12:09:41Z urn:sha1:fdf4a81ca5586d571d65bffbb358515466ebc59c tor-dirclient: Always set the Content-Length header. 2023-10-24T14:42:35Z Gabriela Moldovan gabi@torproject.org 2023-10-24T12:05:34Z urn:sha1:7ae30d9ca63c5b2ec8675374d5a686972a3c4965 tor-dirclient: Add a Content-Length header (fmt). 2023-10-24T14:42:35Z Gabriela Moldovan gabi@torproject.org 2023-10-23T17:05:51Z urn:sha1:8362bb4c240f06a349c526846e67a3d7fd92c8e5 tor-dirclient: Add a Content-Length header. 2023-10-24T14:42:35Z Gabriela Moldovan gabi@torproject.org 2023-10-18T21:55:05Z urn:sha1:01546feeea44d0dbe30f84271c408c75be9744b6 dirclient: Seal the Requestable trait and hide most of its members. 2023-10-17T13:39:31Z Nick Mathewson nickm@torproject.org 2023-10-17T13:39:31Z urn:sha1:7fef9b468a2e3f730ee510eff3d29c98606f1a73 Since none of these methods were invoked from outside `tor-dirclient` (except for debugging), and since we have had a fair amount of churn on what we actually want them to be, it seems like a good idea to use this trick to hide them. This will let us make other changes to the actual behavior of Requestable in the future.