mirrors/arti.git/crates/tor-hsservice/Cargo.toml, branch arti-v1.2.7mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.2.72024-09-03T17:57:12ZBump all the unstable tor- and arti- crates to 0.22.0.2024-09-03T17:57:12ZGabriela Moldovangabi@torproject.org2024-09-03T17:25:54Zurn:sha1:c3c266707f2fd361a447d922c5acfbb3938d88f2
Done using:
```
for crate in $(./maint/list_crates | rg '^(tor|arti-)'); do
cargo set-version -p $crate 0.22.0
done
```
oneshot-fused-workaround: Set the initial version to 0.1.0.2024-09-03T15:22:43ZGabriela Moldovangabi@torproject.org2024-09-03T14:55:25Zurn:sha1:a88af5e93762a8cd95321a3adc31b2bc2ae3bd4d
This is the first time we're publishing this, so let's start at 0.1.0.
Fix formatting issues introduced by fixup-features.2024-09-03T10:00:30ZGabriela Moldovangabi@torproject.org2024-09-03T09:21:55Zurn:sha1:dfe02110114be3f17e439bf99f776521fd044e15Run fixup-features in preparation for release.2024-09-03T10:00:30ZGabriela Moldovangabi@torproject.org2024-09-03T09:10:10Zurn:sha1:1eea611d14630c2901962e5cba408f2b7cf456fcextract tor_async_utils::oneshot into ::oneshot-fused-workaround2024-08-28T14:27:46ZJim Newsomejnewsome@torproject.org2024-08-22T19:20:36Zurn:sha1:46f7f01092e6ac55e3e958dc3a2228b1d36e26a1
Having this in the `tor-async-utils` crate prevents us from doing both
of the following without introducing a circular dependency:
* using it in `tor-rtmock` (which we currently do, particularly in
tests).
* using `tor-rtmock` to test things in `tor-async-utils`. We don't do
this yet, but it is generally sensible to do so. In particular we
want to move the `stream_peak` module there, which is currently tested
with `tor-rtmock`.
Moving this into its own crate avoids this circular dependency.
Add script for *testing* without any features enabled2024-08-19T17:00:48ZIan Jacksonijackson@chiark.greenend.org.uk2024-08-19T15:00:04Zurn:sha1:7a9bf49870533cc052b12680336f067f77d87b34
We can't do this for every crate.
I looked at what is now matrix-check to see if I wanted to use any of
the code. But it seems too entangled with its particular purpose, and
has a lot of embedded knowledge of our crates' features. I found it
sufficiently far from what I wanted that I decided on a fresh script.
tor-hsservice: Add restricted discovery configuration.2024-08-05T16:41:15ZGabriela Moldovangabi@torproject.org2024-07-25T14:05:55Zurn:sha1:eaf76ee0b4b3dc7d77f006b4b8a4cd8323d55bcdtor-hsservice: Add a restricted-discovery feature.2024-08-05T16:41:15ZGabriela Moldovangabi@torproject.org2024-07-08T09:54:00Zurn:sha1:3759e2041408246324aa2bb5f8ed504b8c68fce7
Restricted discovery mode is initially going to be gated behind the
experimental `restricted-discovery` feature.
Part of #1292
Bump versions for tor- and arti- crates to 0.21.02024-08-01T15:09:32ZNick Mathewsonnickm@torproject.org2024-08-01T15:09:32Zurn:sha1:5c2019c5e55a370877b92af67312714b7660847c
This is the result of:
```
for crate in $( ./maint/list_crates |grep '^\(tor\|arti-\)' ); do
cargo set-version -p $crate 0.21.0
done
```
Update to derive-deftly 0.142024-07-08T09:32:22ZIan Jacksonijackson@chiark.greenend.org.uk2024-06-28T11:12:21Zurn:sha1:3e2b52343fa2f37aab7057ea39094e41fea6358d
This removes the deprecated syntaxes. Updating now will prevent us
re-introducing the old syntaxes, which we updated in arti!2209.