mirrors/arti.git/crates/tor-hsrproxy/Cargo.toml, branch arti-v1.2.8mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.2.82024-09-30T13:04:32ZBump arti- and tor- crates to 0.23.02024-09-30T13:04:32ZNick Mathewsonnickm@torproject.org2024-09-30T13:04:32Zurn:sha1:d6890da4b1f87fd5e834aeb0cc9a7cd4b1d99e88
Per our policy, every one of these gets a minor bump.
Generated with:
```
for crate in $(./maint/list_crates | grep '^\(tor\|arti\)-' ); do
cargo set-version --bump minor -p $crate;
done
```
(Note the use of `-` at the end end of the grep pattern to prevent
matching the `arti` crate.)
Minor bumps on non-tor/arti crates2024-09-30T12:56:28ZNick Mathewsonnickm@torproject.org2024-09-30T12:56:28Zurn:sha1:b29dd6d7f90cf077e8809a1ab317e23535e165c8
These crates are not in the tor/arti namespace,
but we have given them MSRV bumps:
```
oneshot-fused-workaround
slotmap-careful
fslock-guard
hashx
equix
caret
fs-mistrust
safelog
test-temp-dir
retry-error
```
We are counting this as a breaking change.
Since all of these crates are at 0.x.x,
we have indicated the breaking change with a minor version bump.
This commit was generated with the following script:
```
BUMPS="
oneshot-fused-workaround
slotmap-careful
fslock-guard
hashx
equix
caret
fs-mistrust
safelog
test-temp-dir
retry-error
"
for crate in $BUMPS; do
cargo set-version --bump minor -p $crate;
done
```
Upgrade MSRV to 1.772024-09-26T01:54:22ZNick Mathewsonnickm@torproject.org2024-09-25T14:46:08Zurn:sha1:ff9e93a2a10ef02f436c6f7d7a05739a818b094a
This will allow us to upgrade to the latest version of rusqlite.
Bump MSRV from 1.70 to 1.75.2024-09-16T21:18:31ZWesley Aptekar-Casselsme@wesleyac.com2024-09-16T21:18:31Zurn:sha1:4d1ec233ceadfd1326d0643bd215051e71f95b84Bump 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.
tor-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