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-24T19:14:57Z Ian Jackson ijackson@chiark.greenend.org.uk 2022-05-24T18:07:25Z urn:sha1:9e526aad7c4ca37e8ee9b082449da6493b6e475b This gets rid of `#[serde(flatten)]` which prevents serde_ignored (and other kinds of introspection) from working properly. The price is now that the toplevel has to deal with two configuration objects. The Resolvable trait is overkill right now, but is going to do More Things in a moment. In particular, we need the impl on tuples, so that the whole config can be processed in one go. 2022-05-13T11:42:30Z Ian Jackson ijackson@chiark.greenend.org.uk 2022-05-13T10:42:51Z urn:sha1:4e2bd6c7983dfa1adab59180e034c68bbe167daf 2022-05-13T11:42:30Z Ian Jackson ijackson@chiark.greenend.org.uk 2022-05-13T10:36:28Z urn:sha1:ef36882807dbd6e5dabdd2d40fe4543fb29443ee Generally, change the paths that mention the crate name to go via a module-level "use". This involves adding tor-config as a direct dependency for a few crates. 2022-05-11T14:53:03Z Ian Jackson ijackson@chiark.greenend.org.uk 2022-05-11T11:03:07Z urn:sha1:e363b79a01b1aa19e9407755d67057524775cd95 This emphasises its nature. We're going to provide a more cooked constructor in a moment. 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. 2022-04-27T12:52:13Z Samanta Navarro ferivoz@riseup.net 2022-04-23T11:51:44Z urn:sha1:c53818d496c910de4dfc4bc8d1f53e419fbf7408 2022-04-26T16:16:22Z Nick Mathewson nickm@torproject.org 2022-04-25T20:13:21Z urn:sha1:6b5cefcccf132725bd6be54d938cfa66ed8e1dc6 2022-04-26T16:16:22Z Nick Mathewson nickm@torproject.org 2022-04-25T19:56:21Z urn:sha1:ae72d2109228e7a9ba41484a3283b93efa6a607d Now that our MSRV is at 1.56, we can use the latest rlimit. It has to be 0.8.3 (not "0.8"), since 0.8.2 has compatibility issues with 1.56.