mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.2.6 2024-08-01T15:09:32Z 2024-08-01T15:09:32Z Nick Mathewson nickm@torproject.org 2024-08-01T15:09:32Z urn:sha1:5c2019c5e55a370877b92af67312714b7660847c This is the result of: ``` for crate in $( ./maint/list_crates |grep '^\(tor\|arti-\)' ); do cargo set-version -p $crate 0.21.0 done ``` 2024-07-08T09:32:22Z Ian Jackson ijackson@chiark.greenend.org.uk 2024-06-28T11:12:21Z urn:sha1:3e2b52343fa2f37aab7057ea39094e41fea6358d This removes the deprecated syntaxes. Updating now will prevent us re-introducing the old syntaxes, which we updated in arti!2209. 2024-06-27T12:24:55Z Ian Jackson ijackson@chiark.greenend.org.uk 2024-06-27T12:24:55Z urn:sha1:cb70cfc32b623cf4d55ae481218a810af04dfea4 nailing-cargo -uE set-version -p arti-client 0.20.0 nailing-cargo -uE set-version -p arti-relay 0.20.0 nailing-cargo -uE set-version -p arti-rpcserver 0.20.0 nailing-cargo -uE set-version -p tor-async-utils 0.20.0 nailing-cargo -uE set-version -p tor-basic-utils 0.20.0 nailing-cargo -uE set-version -p tor-bytes 0.20.0 nailing-cargo -uE set-version -p tor-cell 0.20.0 nailing-cargo -uE set-version -p tor-cert 0.20.0 nailing-cargo -uE set-version -p tor-chanmgr 0.20.0 nailing-cargo -uE set-version -p tor-checkable 0.20.0 nailing-cargo -uE set-version -p tor-circmgr 0.20.0 nailing-cargo -uE set-version -p tor-config 0.20.0 nailing-cargo -uE set-version -p tor-consdiff 0.20.0 nailing-cargo -uE set-version -p tor-dirclient 0.20.0 nailing-cargo -uE set-version -p tor-dirmgr 0.20.0 nailing-cargo -uE set-version -p tor-error 0.20.0 nailing-cargo -uE set-version -p tor-geoip 0.20.0 nailing-cargo -uE set-version -p tor-guardmgr 0.20.0 nailing-cargo -uE set-version -p tor-hsclient 0.20.0 nailing-cargo -uE set-version -p tor-hscrypto 0.20.0 nailing-cargo -uE set-version -p tor-hsrproxy 0.20.0 nailing-cargo -uE set-version -p tor-hsservice 0.20.0 nailing-cargo -uE set-version -p tor-keymgr 0.20.0 nailing-cargo -uE set-version -p tor-linkspec 0.20.0 nailing-cargo -uE set-version -p tor-llcrypto 0.20.0 nailing-cargo -uE set-version -p tor-log-ratelim 0.20.0 nailing-cargo -uE set-version -p tor-memquota 0.20.0 nailing-cargo -uE set-version -p tor-netdir 0.20.0 nailing-cargo -uE set-version -p tor-netdoc 0.20.0 nailing-cargo -uE set-version -p tor-persist 0.20.0 nailing-cargo -uE set-version -p tor-proto 0.20.0 nailing-cargo -uE set-version -p tor-protover 0.20.0 nailing-cargo -uE set-version -p tor-ptmgr 0.20.0 nailing-cargo -uE set-version -p tor-relay-selection 0.20.0 nailing-cargo -uE set-version -p tor-rpcbase 0.20.0 nailing-cargo -uE set-version -p tor-rtcompat 0.20.0 nailing-cargo -uE set-version -p tor-rtmock 0.20.0 nailing-cargo -uE set-version -p tor-socksproto 0.20.0 nailing-cargo -uE set-version -p tor-units 0.20.0 Each of which runs a rune like cargo set-version --offline -p tor-units 0.20.0 2024-06-25T13:38:35Z Ian Jackson ijackson@chiark.greenend.org.uk 2024-06-25T13:37:51Z urn:sha1:fe5fb7072d52610d07d01cd812f0f92a5a42c92f No code changes needed. Precisely nailing-cargo -Eu upgrade --incompatible -p derive-deftly 2024-06-17T18:13:05Z Ian Jackson ijackson@chiark.greenend.org.uk 2024-06-17T17:28:34Z urn:sha1:9fd1b84663081afcccda5eb41455a715947823ff * Bump in Cargo.toml * Deal with `${Xmeta as ...}` incompatible change, by always specifying an `as`, and changing `as tokens`. 2024-06-05T15:06:54Z Gabriela Moldovan gabi@torproject.org 2024-06-05T15:06:54Z urn:sha1:7a11638841eeabd2b5ebfe307541926c29cbfe77 The unstable crates are: - tor-error - tor-config - tor-units - tor-geoip - tor-rtcompat - tor-rtmock - tor-log-ratelim - tor-rpcbase - tor-memquota - tor-llcrypto - tor-protover - tor-bytes - tor-hscrypto - tor-socksproto - tor-checkable - tor-cert - tor-linkspec - tor-cell - tor-proto - tor-netdoc - tor-consdiff - tor-netdir - tor-relay-selection - tor-persist - tor-chanmgr - tor-ptmgr - tor-guardmgr - tor-circmgr - tor-dirclient - tor-dirmgr - tor-keymgr - tor-hsclient - tor-hsservice - tor-hsrproxy - arti-client - arti-rpcserver - arti-hyper - tor-basic-utils - tor-async-utils Done using ``` for p in "${unstable[@]}"; do cargo set-version -p $p 0.19; done ``` where `unstable` contains the list above 2024-06-05T11:47:47Z Gabriela Moldovan gabi@torproject.org 2024-06-05T11:47:47Z urn:sha1:f518076ce0e4bbdb20cb9b7f6aca951f17022569 2024-06-05T11:47:29Z Gabriela Moldovan gabi@torproject.org 2024-06-05T11:47:29Z urn:sha1:fabc5573600f290e4dd20afc9085afe6dfe40c8e 2024-05-14T12:04:03Z Nick Mathewson nickm@torproject.org 2024-05-10T01:32:03Z urn:sha1:d014d60e9e5fe439846e4c05fdd8e73bfc67a1fd The application creates these, using a new-stream-handle RPC command, on an object that can actually create streams. Then later, the application provides the (global) identity of one of these objects when it's making a SOCKS connection. This causes the object to take hold of a `DataStreamCtrl`. 2024-05-12T17:41:09Z Nick Mathewson nickm@torproject.org 2024-05-09T22:54:39Z urn:sha1:a20973afe602d5977fd686f6e005c13a1e9d5100 (These will later become objects that can receive any application request, once we have HTTP connect.) For now, Session and TorClient implement this trait; but soon there will be a new type to hold on to the created DataStreamCtrl. There are some XXXXs here, marking code that is too ugly to live. I should fix it before I merge this branch.