mirrors/arti.git/crates/tor-dirclient/Cargo.toml, branch arti-v1.1.2mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.22023-02-28T12:13:27ZPatchlevel bumps for remaining changed crates.2023-02-28T12:13:27ZNick Mathewsonnickm@torproject.org2023-02-28T12:13:27Zurn: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
Bump minor versions for significant breaking changes.2023-02-28T12:05:15ZNick Mathewsonnickm@torproject.org2023-02-28T12:05:15Zurn:sha1:3e257a7cb57801329f013e7c1dc2d8c2dc598e47
This includes tor-cell, tor-proto, and tor-netdir.
Bump the patch version of every crate that had API additions2023-02-01T15:36:29ZNick Mathewsonnickm@torproject.org2023-02-01T15:36:29Zurn: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.
Bump the patch-level version of crates with _minor_ changes.2023-02-01T15:23:58ZNick Mathewsonnickm@torproject.org2023-02-01T15:23:58Zurn: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.)
Complete our migration to base64ct.2023-01-20T13:06:30ZNick Mathewsonnickm@torproject.org2023-01-19T19:50:07Zurn: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.
Bump the minor version of every crate.2022-11-30T20:10:16ZNick Mathewsonnickm@torproject.org2022-11-30T20:10:16Zurn: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.
bump rust-version to 1.60 in every crate.2022-11-10T15:57:33ZNick Mathewsonnickm@torproject.org2022-11-07T19:18:02Zurn:sha1:936920b26e43447a010e249a9b5a5b9f69ca0da1Require derive_more 0.99.32022-11-03T11:37:23ZIan Jacksonijackson@chiark.greenend.org.uk2022-11-01T10:59:37Zurn: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.
Bump minor version of tor-rtcompat and most of its dependents2022-10-03T14:01:46ZNick Mathewsonnickm@torproject.org2022-10-03T14:01:46Zurn:sha1:102e3c221dfadd6578cc6001f0566897fa9acaf8
(Since the APIs for the `Schedule::sleep*` functions changed, this
is a breaking change in tor-rtcompat. Therefore, the Runtime trait
in tor-rtcompat is now a different trait. Therefore, anything that
uses the Runtime trait in its APIs has also broken.)
Bump crates that have had backward compatible API changes.2022-10-03T13:52:34ZNick Mathewsonnickm@torproject.org2022-10-03T13:52:34Zurn:sha1:388e0cbab55490f41e1c8cd06631efed7f23a318