mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.4.0 2022-05-27T14:18:52Z 2022-05-27T14:18:52Z Nick Mathewson nickm@torproject.org 2022-05-27T14:18:52Z urn:sha1:4326aa1de9875ea399c3a608c0320bbe4b214a42 This commit was made by reverting the previous commit, then re-running the script I used to generate it. In theory there should be no semantic changes: only changes due to improved formatting from cargo edit. 2022-05-27T13:01:20Z Nick Mathewson nickm@torproject.org 2022-05-27T13:01:20Z urn:sha1:b232365a75249d6f767127feb2a47286f9ece762 I followed the following procedure to make these changes: * I used maint/changed_crates to find out which crates had changed since 0.3.0. * I used grep and maint/list_crates to sort those crates in topological (dependency) order. * I looked through semver_status to find which crates were listed as having semver-relevant changes (new APIs and breaking changes). * I scanned through the git logs of the crates with no semver-relevant changes listed to confirm that, indeed, they had no changes. For those crates, I incremented their patch-level version _without_ changing the version that other crates depend on. * I scanned through the git logs of the crates with no semver-relevant changes listed to confirm that, indeed, they had no obvious breaking changes. * I treated all crates that depend on `arti` and/or `arti-client` as having breaking changes. * I identified crates that depend on crates that have changed, even if they have not changed themselves, and identified them as having a non-breaking change. * For all of the crates, I used `cargo set-version -p $CRATE --bump $STATUS` (where `STATUS` is `patch` or `minor`) to update the versions, and the depended-upon versions. 2022-05-27T12:52:44Z Nick Mathewson nickm@torproject.org 2022-05-27T12:52:44Z urn:sha1:45d21d2520cf083000e4384242f33796186de29b These crates had only clippy fixes that do not affect their behavior: tor-bytes tor-cell tor-events tor-linkspec tor-netdir tor-socksproto This crate only had the cargo-husky dependency removed, which does not affect compatibility: tor-llcrypto Since these changes have no compatibility effects, it is not necessary to bump the versions of these crates which other crates depend on. 2022-05-27T12:34:52Z Nick Mathewson nickm@torproject.org 2022-05-27T12:34:52Z urn:sha1:fbc5218af66cd2c22d895c41a7389e91e7f45754 2022-05-26T19:40:39Z Nick Mathewson nickm@torproject.org 2022-05-26T19:40:39Z urn:sha1:b4a87687f511119a26d27b226167917438f526d4 2022-05-26T14:35:32Z Nick Mathewson nickm@torproject.org 2022-05-26T14:35:32Z urn:sha1:ae08a023fb50af1fa64844a731ecdd48cb91105b Add a few coverage-driven tests See merge request tpo/core/arti!536 2022-05-26T13:59:48Z Nick Mathewson nickm@torproject.org 2022-05-26T13:59:48Z urn:sha1:c33a9d1f4e81b38bba7907a2fd852fc46e0f6bf6 2022-05-26T12:53:14Z Nick Mathewson nickm@torproject.org 2022-05-26T12:53:14Z urn:sha1:68b04197528896bf84774c738cf6439e73977c5e Standardise shell Closes #425 See merge request tpo/core/arti!533 2022-05-26T10:40:43Z Ian Jackson iwj@torproject.org 2022-05-26T10:40:43Z urn:sha1:4bf87d61ca94648a7af220342303748f1ae1d1b3 Break TorClientConfig out of ArtiConfig and warn on unknown config keys Closes #459 and #417 See merge request tpo/core/arti!529 2022-05-26T10:03:48Z Ian Jackson ijackson@chiark.greenend.org.uk 2022-05-26T10:03:25Z urn:sha1:c5a8e453b9610c53921e41b749bcf977b1e084f9 We can have mem::take, hooray.