mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.4 2023-05-03T12:31:11Z 2023-05-03T12:31:11Z Nick Mathewson nickm@torproject.org 2023-05-03T12:31:11Z urn:sha1:1904cfc8b9ca5dd0974dc39516a58a57226f123f Because of the errorkind bumps, we're calling this a breaking change in everything lower-level than `arti`. Generated with: ``` cargo set-version -p tor-basic-utils --bump minor cargo set-version -p tor-async-utils --bump minor cargo set-version -p caret --bump minor cargo set-version -p fs-mistrust --bump minor cargo set-version -p safelog --bump minor cargo set-version -p retry-error --bump minor cargo set-version -p tor-error --bump minor cargo set-version -p tor-config --bump minor cargo set-version -p tor-events --bump minor cargo set-version -p tor-units --bump minor cargo set-version -p tor-rtcompat --bump minor cargo set-version -p tor-rtmock --bump minor cargo set-version -p tor-rpcbase --bump minor cargo set-version -p tor-llcrypto --bump minor cargo set-version -p tor-protover --bump minor cargo set-version -p tor-bytes --bump minor cargo set-version -p tor-hscrypto --bump minor cargo set-version -p tor-socksproto --bump minor cargo set-version -p tor-checkable --bump minor cargo set-version -p tor-cert --bump minor cargo set-version -p tor-linkspec --bump minor cargo set-version -p tor-cell --bump minor cargo set-version -p tor-proto --bump minor cargo set-version -p tor-netdoc --bump minor cargo set-version -p tor-consdiff --bump minor cargo set-version -p tor-netdir --bump minor cargo set-version -p tor-congestion --bump minor cargo set-version -p tor-persist --bump minor cargo set-version -p tor-chanmgr --bump minor cargo set-version -p tor-ptmgr --bump minor cargo set-version -p tor-guardmgr --bump minor cargo set-version -p tor-circmgr --bump minor cargo set-version -p tor-dirclient --bump minor cargo set-version -p tor-dirmgr --bump minor cargo set-version -p tor-hsclient --bump minor cargo set-version -p tor-hsservice --bump minor cargo set-version -p arti-client --bump minor cargo set-version -p arti-rpcserver --bump minor cargo set-version -p arti-config --bump minor cargo set-version -p arti-hyper --bump minor cargo set-version -p arti --bump patch cargo set-version -p arti-bench --bump patch cargo set-version -p arti-testing --bump patch ``` 2023-04-11T19:31:12Z Nick Mathewson nickm@torproject.org 2023-04-11T19:31:12Z urn:sha1:104d64589db24187c56fd8c7b13fdd9202ecc120 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-22T19:15:42Z Nick Mathewson nickm@torproject.org 2023-03-22T19:15:42Z urn:sha1:19cdb239bf4f850b9f09412b2842d8a09d0e5608 2023-02-28T12:13:27Z Nick Mathewson nickm@torproject.org 2023-02-28T12:13:27Z urn:sha1:f41449d0bd9a2db5f72dd9941fb897e5cd9b922d These crates have had small code changes, but no API additions: tor-config tor-socksproto tor-cert tor-chanmgr tor-ptmgr tor-guardmgr tor-circmgr tor-dirclient tor-dirmgr arti tor-hsservice tor-congestion These crates have had API extensions: fs-mistrust tor-llcrypto tor-bytes tor-checkable tor-linkspec tor-netdoc tor-persist arti-client 2023-02-14T16:06:00Z Nick Mathewson nickm@torproject.org 2023-02-14T16:05:48Z urn:sha1:f1ec64bfe5fbb7754058ccf1ddd22b2b1af1f7dc (None of the breaking changes affect us this time.) 2023-02-01T15:36:29Z Nick Mathewson nickm@torproject.org 2023-02-01T15:36:29Z urn:sha1:7c1b6a5a81e382be6210c7e2b0aae9695ad0bef4 These crates had API or behavior changes that may affect downstream crates. Fortunately, they're all version 0.x, and don't need minor bumps for this. 2023-02-01T15:23:58Z Nick Mathewson nickm@torproject.org 2023-02-01T15:23:58Z urn:sha1:66f594a4b6fac81137886be90a7bda3687923d48 These changes influence behavior, but not effect compatibility. (If I messed up, and any crate except for `arti` has non-breaking API changes, that's still fine, since they are all version 0.x.) 2023-01-25T21:29:53Z Nick Mathewson nickm@torproject.org 2023-01-25T21:29:53Z urn:sha1:f9903789d1134f5c484fdab3d4f3d4a710e3d76e This required rewriting some of our error handling code in command-line processing, since the toml crate now displays and reports errors differently. (Admittedly, this code still is kind of ugly, but at least it is nicely hidden.) 2022-12-06T15:15:22Z Ian Jackson ijackson@chiark.greenend.org.uk 2022-12-06T15:11:39Z urn:sha1:ba338bdf371250210474346bf0ac492d3bc70672 This is the new upstream version (published by me, recently). It has the same MSRV and one breaking change: The caller who specifies a home dir function for substituting into strings, must now supply a string, not Path. Previously shellexpand would allow the caller to supply non-unicode data, and then simply not substitute it. That was an infelicity in the shellexpand API. Now this infelicity is pushed into our code. The overall behaviour of Arti hasn't changed as a result. And it seems reasonable to me. shellexpand 3.x also has a module for expanding Paths instead, in response to requests for this filed as upstream tickets. We *could* use that but I am not sanguine about that approach: the Pathness would spread throughout much of our config and file handling code. I think we should at the very least postpone trying to work with invalid-unicode-paths as long as we can.