mirrors/arti.git/crates/tor-netdir/Cargo.toml, branch arti-v1.1.1mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.12023-02-01T15:36:29ZBump 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.)
netdir: remove the vestigial smallvec implementation I added2023-01-28T17:43:08ZNick Mathewsonnickm@torproject.org2023-01-27T18:38:33Zurn:sha1:4e7a552171040e79d67e50e1a6691c1e51d45d0a
It's cute, but I don't think it will help performance, and I'm
undecided about whether the semantic implications are true.
netdir: Implement ring-param constructors and time period accessors2023-01-28T17:43:08ZNick Mathewsonnickm@torproject.org2023-01-24T15:46:56Zurn:sha1:5236c5cf887af0bd321ca80fb6dba991289549d6
This logic is a bit tricky, so I've tried to document it and add
fairly good tests. The silver lining is that the external API for
all of this logic will make it invisible and hidden.
There are some cases where I added functions that I think might
eventually get lowered into MdConsensus: But I don't want to lower
too much right now, since the convention for our netdoc accessors is
that they are fairly unsophisticated, and they show you the document
as it is.
Closes #686
Adjust onion service ring APIs in light of prop#3422023-01-11T14:04:13ZNick Mathewsonnickm@torproject.org2023-01-10T14:23:42Zurn:sha1:5b74ef7af9be657918b1b2c8672f35b269c23198
* It is the NetDir's responsibility to tell the caller what the time
period is.
* There can be up to two secondary time periods.
* Each time period has a single SRV.
* Secondary time periods only apply for onion services, when they
publish.
* When publishing, the correct input is a time period.
Sketch APIs for the onion service directory ring.2023-01-11T14:04:13ZNick Mathewsonnickm@torproject.org2023-01-09T17:10:29Zurn:sha1:f24f8d295cf3ec324034c824fbbb40a694acb6f1
These are a bit complex internally, but the API they present is
pretty simple. I've left some discussion of points where the design
isn't totally fleshed out, and where we need to look harder at the
spec.
Part of #716.
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.
remove unused dependancies2022-10-29T11:29:55Ztrinity-1686atrinity@deuxfleurs.fr2022-10-29T10:23:17Zurn:sha1:e6e064ac8ad20906fb55c295d5de109c0f54433d