mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.2 2023-02-01T15:36:29Z 2023-02-01T15:36:29Z Nick Mathewson nickm@torproject.org 2023-02-01T15:36:29Z urn:sha1:7c1b6a5a81e382be6210c7e2b0aae9695ad0bef4 These crates had API or behavior changes that may affect downstream crates. Fortunately, they're all version 0.x, and don't need minor bumps for this. 2022-11-30T20:10:16Z Nick Mathewson nickm@torproject.org 2022-11-30T20:10:16Z urn:sha1:38bef96b99dbf17922dc601d4250abc0368b519f We made this job easy this time around: by incrementing our MSRV, we have forced ourselves to do at least a minor bump everywhere. 2022-11-10T15:57:33Z Nick Mathewson nickm@torproject.org 2022-11-07T19:18:02Z urn:sha1:936920b26e43447a010e249a9b5a5b9f69ca0da1 2022-11-03T11:37:23Z Ian Jackson ijackson@chiark.greenend.org.uk 2022-11-01T10:59:37Z urn:sha1:48f48841e1aa99f0c76c2078812b003ec191540a 0.99.[012] have a bug https://github.com/JelteF/derive_more/issues/114 which makes the Deref derive for bridgedesc::StateGuard not work and therefore breaks minimal-versions CI. It seems simpler to require the newer version everywhere. 2022-10-03T13:47:09Z Nick Mathewson nickm@torproject.org 2022-10-03T13:47:09Z urn:sha1:f5389b53e9375cfe44171207546c1c21450da23d 2022-09-01T12:45:02Z Nick Mathewson nickm@torproject.org 2022-09-01T12:45:02Z urn:sha1:b3f989d6894aba3a12ff6ca629aee508566baf76 Since our last round of releases, these crates have had either trivial changes, or changes that did not affect their APIs. Therefore we are bumping their versions, but not changing which versions of them other crates depend on. 2022-08-24T16:22:41Z trinity-1686a trinity@deuxfleurs.fr 2022-08-17T19:13:13Z urn:sha1:7f939fa4804b3c934343141b79e8e2ded5fe0b0d 2022-06-24T16:00:22Z Nick Mathewson nickm@torproject.org 2022-06-24T16:00:22Z urn:sha1:20435aea751331817709acde8d4b65b5fb8d8f12 These were done with the following commands: ``` cargo set-version -p tor-basic-utils --bump patch cargo set-version -p fs-mistrust --bump minor cargo set-version -p tor-error --bump patch cargo set-version -p tor-config --bump patch cargo set-version -p tor-units --bump patch cargo set-version -p tor-rtcompat --bump minor cargo set-version -p tor-llcrypto --bump patch cargo set-version -p tor-bytes --bump minor cargo set-version -p tor-socksproto --bump minor cargo set-version -p tor-cert --bump minor cargo set-version -p tor-cell --bump minor cargo set-version -p tor-proto --bump minor cargo set-version -p tor-netdoc --bump patch cargo set-version -p tor-netdir --bump minor cargo set-version -p tor-persist --bump patch cargo set-version -p tor-chanmgr --bump minor cargo set-version -p tor-guardmgr --bump minor cargo set-version -p tor-circmgr --bump patch cargo set-version -p tor-dirclient --bump patch cargo set-version -p tor-dirmgr --bump minor cargo set-version -p arti-client --bump patch cargo set-version -p arti --bump minor cargo set-version -p arti-bench --bump minor cargo set-version -p arti-testing --bump minor ``` 2022-05-27T18:02:17Z Nick Mathewson nickm@torproject.org 2022-05-27T18:02:17Z urn:sha1:9d36925700d69034caecb401c973d186d507ff8f There is no "tor" category; crates.io warned about this. 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.