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-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-25T20:25:58Z trinity-1686a trinity@deuxfleurs.fr 2022-05-25T15:37:19Z urn:sha1:b380c25e6637b2cf48239eea8c4a3707eb3aa67e 2022-05-25T19:57:19Z Nick Mathewson nickm@torproject.org 2022-05-25T16:42:24Z urn:sha1:60023ef6565992e7d7e382ab1745eb4d7d6e81d0 Also, if we get an IoError from a call to fs-mistrust, report it as an IoError. 2022-05-24T14:54:02Z Nick Mathewson nickm@torproject.org 2022-05-18T17:26:01Z urn:sha1:95200383b52d1644d4de357c2a8a50d91fdc1021 This is an approximately minimal revision to get Builder in place; subsequent commits will clean up the API. 2022-05-23T20:02:50Z Nick Mathewson nickm@torproject.org 2022-05-23T20:02:50Z urn:sha1:c27b3cb70179eea0dc29d6029995d1d93b10987e 2022-05-09T19:27:25Z Nick Mathewson nickm@torproject.org 2022-05-09T19:27:25Z urn:sha1:4262e9d0ecca5f77f6ee2e0b00fb8c35d65f01e3 2022-05-09T18:40:29Z Nick Mathewson nickm@torproject.org 2022-05-03T15:59:33Z urn:sha1:984190b3a3d36cdf90ddcf6a9925722fbe5912a1