mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.11 2023-12-04T16:35:23Z 2023-12-04T16:35:23Z Nick Mathewson nickm@torproject.org 2023-12-04T16:22:58Z urn:sha1:fba95e4b4708929ed09554632acd2e9f15e3c086 This crate is new, and gets a bump to 0.1.0. tor-log-ratelim This crate had a breaking change: tor-persist tor-llcrypto had a breaking change. These crates _are_ tor-llcrypto, or (transitively) depend on it. I am assuming that they all re-expose something from it in a way that matters: tor-llcrypto tor-bytes tor-hscrypto tor-socksproto tor-checkable tor-cert tor-linkspec tor-cell tor-proto tor-netdoc tor-consdiff tor-netdir 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 2023-11-28T16:35:51Z Nick Mathewson nickm@torproject.org 2023-11-28T16:35:51Z urn:sha1:1b53c4ca3059fc395c98e2e6d0eb3b58f37c8ec1 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. ``` 2023-10-25T15:32:36Z Gabriela Moldovan gabi@torproject.org 2023-10-25T14:52:29Z urn:sha1:f18950aa2dcfe2a71a7e626b872a84bed457537f 2023-10-02T18:55:03Z Nick Mathewson nickm@torproject.org 2023-10-02T18:55:03Z urn:sha1:0cfbb6faed2cacc46040bd0df283f31a7600c1a7 (The only change in these crates is that their dependencies changed.) 2023-10-02T18:48:11Z Nick Mathewson nickm@torproject.org 2023-10-02T18:48:11Z urn:sha1:9b1e09c6bb661533081edf0bb58a57d72c92f3d9 2023-09-05T16:22:19Z Nick Mathewson nickm@torproject.org 2023-09-05T16:22:19Z urn:sha1:e251baa9a77415f3c605ff462a8ac0b3fa37660a These are: ``` hashx equix tor-async-utils tor-error tor-config tor-rtmock tor-llcrypto tor-bytes tor-hscrypto tor-hspow tor-cert tor-linkspec tor-cell tor-proto tor-netdoc tor-netdir tor-chanmgr tor-guardmgr tor-dirmgr tor-keymgr tor-hsclient tor-hsservice arti-client arti ``` 2023-08-01T15:03:56Z Nick Mathewson nickm@torproject.org 2023-08-01T15:01:13Z urn:sha1:5cc3fe162944aff8efb975ac966f0e91b6908281 These crates have had trivial changes only: typically, changes to documentation or to clippy warnings. There's no good reason to update which version of them other crates depend on, so we only bump _their_ patchlevels. ``` tor-async-utils caret safelog tor-events tor-units tor-rtcompat tor-rpcbase tor-llcrypto tor-protover tor-bytes tor-hscrypto tor-socksproto tor-cert tor-cell tor-consdiff tor-congestion arti-rpcserver arti-testing arti-bench arti-config arti-hyper ``` 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-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 ```