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-24T13:22:01Z Ian Jackson iwj@torproject.org 2022-05-24T13:22:01Z urn:sha1:85faa1c0f6bc9ea0801c02797accb02e9572d616 Update to newer sanitize-filename and tinystr. See merge request tpo/core/arti!523 2022-05-23T20:02:50Z Nick Mathewson nickm@torproject.org 2022-05-23T20:02:50Z urn:sha1:c27b3cb70179eea0dc29d6029995d1d93b10987e 2022-05-23T16:55:37Z Nick Mathewson nickm@torproject.org 2022-05-23T16:32:31Z urn:sha1:546ae3000eb179aedc97de30b0ccdb1d45b93395 It's a little overzealous sometimes, but it's mostly to the good. 2022-05-14T17:02:53Z Dimitris Apostolou dimitris.apostolou@icloud.com 2022-05-14T17:02:53Z urn:sha1:58dc57688744a102541f17abc33196ea4de4e68a 2022-05-11T16:11:17Z Nick Mathewson nickm@torproject.org 2022-05-11T16:06:52Z urn:sha1:12d1752ad57d9561394631ad2d04c5488e64c48f 2022-05-09T19:59:38Z Nick Mathewson nickm@torproject.org 2022-03-10T21:38:23Z urn:sha1:3b0336e841f537196408f43a4928df20398c160d Relay nicknames are always between 1 and 19 characters long, and they're always ASCII: That means that storing them in a [u8;19] will always be possible, and always use less resources than storing them in a String. Fortunately, the tinystr crate already helps us with this kind of thing. 2022-05-09T14:35:50Z Ian Jackson ijackson@chiark.greenend.org.uk 2022-05-09T14:35:50Z urn:sha1:cc99efb72acc576dec08b43c365d4bb9f54eee1a 2022-05-06T14:03:15Z Nick Mathewson nickm@torproject.org 2022-05-06T14:03:15Z urn:sha1:7b93091f57f43ec8543a17052d60a2c8f7f2b0cc * Except for safelog and fs-mistrust, which are new.