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: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-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. 2022-05-26T09:57:26Z Ian Jackson ijackson@chiark.greenend.org.uk 2022-05-26T09:56:55Z urn:sha1:42ccb684465056b9546cecf697aa354393576a16 As per https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/529#note_2807331 2022-05-26T09:57:04Z Ian Jackson ijackson@chiark.greenend.org.uk 2022-05-26T09:55:48Z urn:sha1:f5561c8cdbbc4864d1bf71297d123bf3a7c724ee This was a slip. As per https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/529#note_2807330 2022-05-25T18:15:47Z Ian Jackson ijackson@chiark.greenend.org.uk 2022-05-25T18:14:11Z urn:sha1:ed95d50d49019028447b2910312dad338f761340 2022-05-25T18:15:47Z Ian Jackson ijackson@chiark.greenend.org.uk 2022-05-25T18:11:16Z urn:sha1:ce96f0d9ce9873eb35744d87db5d222f9f94a4f8