mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=tor-llcrypto-v0.4.4 2023-03-31T12:30:14Z 2023-03-31T12:30:14Z Nick Mathewson nickm@torproject.org 2023-03-31T12:30:14Z urn:sha1:9ef115a7fb21fe7267d1d91ba7babac8e1b7542e These crates had no changes until just a moment ago. But since we updated the versions on some of their dependents, they have now changed themselves. Thus they get patchlevel bumps. ``` tor-rtmock tor-protover tor-socksproto tor-consdiff tor-chanmgr tor-dirclient tor-hsservice ``` 2023-03-31T12:24:39Z Nick Mathewson nickm@torproject.org 2023-03-31T12:24:39Z urn:sha1:a81ab391ae9cc3b48cf08cf1b911f1b4cfa8be76 For these crates, the changes are nontrivial, so we _do_ bump the versions on which their dependent crates depend. Fortunately, since they are all pre-1.0, we don't need to distinguish semver-additions from other changes. (Except for arti, which _is_ post-1.0, but gets a patchlevel bump anyway.) These are unstable crates with breaking changes: ``` tor-hscrypto tor-hsclient ``` These have new or extended APIs: ``` safelog tor-bytes tor-cell tor-linkspec tor-llcrypto tor-proto tor-cert arti-client ``` These have new unstable APIs or features: ``` tor-netdoc tor-circmgr (also broke some unstable APIs) arti (is post-1.0) ``` These have bugfixes only: ``` caret tor-dirmgr ``` 2023-02-28T12:13:27Z Nick Mathewson nickm@torproject.org 2023-02-28T12:13:27Z urn:sha1:f41449d0bd9a2db5f72dd9941fb897e5cd9b922d These crates have had small code changes, but no API additions: tor-config tor-socksproto tor-cert tor-chanmgr tor-ptmgr tor-guardmgr tor-circmgr tor-dirclient tor-dirmgr arti tor-hsservice tor-congestion These crates have had API extensions: fs-mistrust tor-llcrypto tor-bytes tor-checkable tor-linkspec tor-netdoc tor-persist arti-client 2023-02-28T12:05:15Z Nick Mathewson nickm@torproject.org 2023-02-28T12:05:15Z urn:sha1:3e257a7cb57801329f013e7c1dc2d8c2dc598e47 This includes tor-cell, tor-proto, and tor-netdir. 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. 2023-02-01T15:23:58Z Nick Mathewson nickm@torproject.org 2023-02-01T15:23:58Z urn:sha1:66f594a4b6fac81137886be90a7bda3687923d48 These changes influence behavior, but not effect compatibility. (If I messed up, and any crate except for `arti` has non-breaking API changes, that's still fine, since they are all version 0.x.) 2023-01-20T13:06:30Z Nick Mathewson nickm@torproject.org 2023-01-19T19:50:07Z urn:sha1:889206cde4ef29d7d10bda546f8ad518eb09c290 This is in lieu of upgrading to the latest base64 crate, which has a different API from the old one. Since we have to migrate either way, we might as well use base64ct everywhere. I don't think that most of these cases _require_ constant-time base64, but it won't hurt. 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.