mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.2.0 2024-03-04T12:24:40Z 2024-03-04T12:24:40Z Gabriela Moldovan gabi@torproject.org 2024-02-29T18:54:31Z urn:sha1:c1c81600935df2420981d881f08fe8e9e2642525 Functional changes were made, but no APIs were added or broken: ``` tor-events (async_broadcast 0.6.0 -> 0.7.0) tor-netdoc (signature 1 -> 2) tor-guardmgr arti-testing (config 0.13.4 -> 0.14.0) tor-persist (breaking changes gated behind experimental feature) fslock-guard (fix lockfile_has_path compilation on Windows) ``` Done with: ``` cargo set-version --bump patch -p tor-events cargo set-version --bump patch -p tor-netdoc cargo set-version --bump patch -p tor-guardmgr cargo set-version --bump patch -p arti-testing cargo set-version --bump patch -p tor-persist cargo set-version --bump patch -p fslock-guard ``` 2024-02-26T13:06:26Z Nick Mathewson nickm@torproject.org 2024-02-26T13:06:26Z urn:sha1:bf624a9dfa9b2532c481b0373fbb3470d2aff551 2023-11-28T16:35:51Z Nick Mathewson nickm@torproject.org 2023-11-28T16:35:51Z urn:sha1:1b53c4ca3059fc395c98e2e6d0eb3b58f37c8ec1 2023-10-17T16:30:39Z Nick Mathewson nickm@torproject.org 2023-10-17T16:30:39Z urn:sha1:79f072896857987d65b5efaeb1a53eaa9e2f1ba2 (This is only used in the disabled tor-events crate, but it's still easier to keep dependencies up-to-date than not.) 2023-09-05T16:25:24Z Nick Mathewson nickm@torproject.org 2023-09-05T16:25:24Z urn:sha1:a4badb9fdac5dd36ea173545f1ff417ccab1f49b This includes: ``` tor-basic-utils caret fs-mistrust safelog retry-error tor-events tor-units tor-geoip tor-rtcompat tor-rpcbase tor-protover tor-socksproto tor-checkable tor-congestion tor-persist tor-circmgr arti-rpcserver arti-config arti-hyper arti-bench arti-testing tor-consdiff ``` 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-07-03T17:49:51Z Nick Mathewson nickm@torproject.org 2023-07-03T17:49:51Z urn:sha1:2c5b81e872461e867a943da9cc4aff1f1ad90c94 These crates were started, but they aren't integrated into Arti (yet?). As such it doesn't make sense to keep publishing updated versions of them every time we tweak our standard lints. 2023-06-30T12:30:55Z Nick Mathewson nickm@torproject.org 2023-06-30T12:30:55Z urn:sha1:40768a9f6174609b1146c981e235b99e5953f364 These crates have had nonfunctional changes only, mostly due to !1271, or ac90cb7500f2f108, or documentation changes: crates that depend on them do not require a version bump. ``` arti-bench arti-config arti-hyper arti-testing caret fs-mistrust retry-error tor-async-utils tor-basic-utils tor-chanmgr tor-checkable tor-congestion tor-consdiff tor-events tor-guardmgr tor-persist tor-protover tor-ptmgr tor-rtcompat tor-rtmock tor-units ``` 2023-06-01T14:03:05Z Nick Mathewson nickm@torproject.org 2023-06-01T14:03:05Z urn:sha1:daf5ecc15340c5910fdb912ea9099719befd916e Generated with the following commands: ``` cargo set-version --bump minor -p tor-cell cargo set-version --bump minor -p tor-linkspec cargo set-version --bump minor -p tor-proto cargo set-version --bump minor -p tor-netdoc cargo set-version --bump minor -p tor-circmgr cargo set-version --bump patch -p tor-cert cargo set-version --bump patch -p tor-basic-utils cargo set-version --bump patch -p tor-rpcbase cargo set-version --bump patch -p tor-llcrypto cargo set-version --bump patch -p tor-hscrypto cargo set-version --bump patch -p tor-checkable cargo set-version --bump patch -p tor-async-utils cargo set-version --bump patch -p caret cargo set-version --bump patch -p fs-mistrust cargo set-version --bump patch -p safelog cargo set-version --bump patch -p retry-error cargo set-version --bump patch -p tor-error cargo set-version --bump patch -p tor-config cargo set-version --bump patch -p tor-events cargo set-version --bump patch -p tor-units cargo set-version --bump patch -p tor-rtcompat cargo set-version --bump patch -p tor-rtmock cargo set-version --bump patch -p tor-protover cargo set-version --bump patch -p tor-bytes cargo set-version --bump patch -p tor-socksproto cargo set-version --bump patch -p tor-consdiff cargo set-version --bump patch -p tor-netdir cargo set-version --bump patch -p tor-congestion cargo set-version --bump patch -p tor-persist cargo set-version --bump patch -p tor-chanmgr cargo set-version --bump patch -p tor-ptmgr cargo set-version --bump patch -p tor-guardmgr cargo set-version --bump patch -p tor-dirclient cargo set-version --bump patch -p tor-dirmgr cargo set-version --bump patch -p tor-hsclient cargo set-version --bump patch -p tor-hsservice cargo set-version --bump patch -p arti-client cargo set-version --bump patch -p arti-rpcserver cargo set-version --bump patch -p arti-config cargo set-version --bump patch -p arti-hyper cargo set-version --bump patch -p arti cargo set-version --bump patch -p arti-bench cargo set-version --bump patch -p arti-testing ``` 2023-05-15T13:07:21Z Nick Mathewson nickm@torproject.org 2023-05-15T12:16:43Z urn:sha1:7a5373c11007f29007341dc871c14ae1fa026cef This does the following: - Gives every crate a `full`. - Cause every `full` to depend on `full` from the lower-level crates. - Makes every feature listed _directly_ in `experimental` depend on `__is_experimental`.