mirrors/arti.git/crates/arti-client, branch arti-v1.1.13mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.132024-02-05T16:51:38ZMerge branch 'delete-semvers' into 'main'2024-02-05T16:51:38ZIan Jacksoniwj@torproject.org2024-02-05T16:51:38Zurn:sha1:2f71ce50f1a7992d4b6c66de38786bfa2abc6bde
Remove all semver.md files to start a fresh release round
See merge request tpo/core/arti!1957Bump patch versions *with* dependency update2024-02-05T16:20:53ZIan Jacksonijackson@chiark.greenend.org.uk2024-02-05T16:20:26Zurn:sha1:97e284b90323dd3aeaf05839a00b801c2ee194f9
This crate has had new features added. It's 0.x. So bump in-tree
dependencies' references:
fs-mistrust
Bump minor versions2024-02-05T16:13:29ZIan Jacksonijackson@chiark.greenend.org.uk2024-02-05T16:13:29Zurn:sha1:af615d87e20d0984f493dfb8dda7b0654d8d7304
Bump the minor version of these crates, and update the in-tree
dependencies.
Recently published as fresh crates, let's just assume there are
breaking changes:
fslock-guard
test-temp-dir
Breaking API change affecting many many downstream crates:
tor-rtcompat
Downstream crates which we're (conservatively) assuming have
tor-rtcompat types in their APIs:
tor-rtmock
tor-log-ratelim
tor-rpcbase
tor-llcrypto
tor-protover
tor-bytes
tor-hscrypto
tor-hspow
tor-socksproto
tor-checkable
tor-cert
tor-linkspec
tor-cell
tor-proto
tor-netdoc
tor-consdiff
tor-netdir
tor-congestion
tor-persist
tor-chanmgr
tor-ptmgr
tor-guardmgr
tor-circmgr
tor-dirclient
tor-dirmgr
tor-keymgr
tor-hsclient
tor-hsservice
tor-hsrproxy
arti-client
arti-rpcserver
arti-config
arti-hyper
arti-bench
arti-testing
Remove all semver.md files to start a fresh release round2024-02-05T15:27:50ZIan Jacksonijackson@chiark.greenend.org.uk2024-02-05T15:27:21Zurn:sha1:760274c281779248528e8a23c986503b32e81fd8tor-hsservice: Use tor_persist::state_dir2024-02-01T11:21:44ZIan Jacksonijackson@chiark.greenend.org.uk2024-01-31T14:13:25Zurn:sha1:b1d40b7d8c562cfee352cdf7852c065938acf702tor-hsservice: Use tor_persist::state_dir, etc. (fmt)2024-02-01T11:21:44ZIan Jacksonijackson@chiark.greenend.org.uk2024-01-30T16:12:33Zurn:sha1:4ccf20f165cb39e8f3da0a56eab55ea4fe1e4dd1tor-hsservice: Use tor_persist::state_dir2024-02-01T11:21:44ZIan Jacksonijackson@chiark.greenend.org.uk2024-01-30T15:42:13Zurn:sha1:b4a7f0fca0d231eb9c0298b78deee9ed3c1bbc7e
We no longer do replay log locking in IptManager::new. Instead, we
rely on the acquire_instance call in OnionService::launch, which ends
up with ipt_mgr getting an InstanceHandle (which contains a lock
guard).
OnionServiceStateMgr is abolished; it existed to deal with the
generics in the tor_persist::StateMgr API. state_dir has no
generics (other than the T being loaded/stored).
Many places (structs and argument lists) now have state_dir types
which embody a path (or a CheckeDir) along with a lock, rather than
separate path+lock+mistrust.
The creation/startup code uses the new calls from state_dir.
Other more minor changes:
- StartupError::StateDirectoryInaccessible contains tor_persist::Error
- test::create_storage_handles_from_state_dir changed and renamed,
from _from_state_mgr.
- replay::PersistFile's (separate) file lock is now fslock_guard's
tor-hsclient: Rename HsClientSpecifier to HsClientNickname (fmt).2024-01-31T10:43:06ZGabriela Moldovangabi@torproject.org2024-01-30T19:14:09Zurn:sha1:a60aaaa9851733bc93139e800d4b49276df024d6tor-hsclient: Rename HsClientSpecifier to HsClientNickname.2024-01-31T10:43:06ZGabriela Moldovangabi@torproject.org2024-01-30T19:12:14Zurn:sha1:86ee7ebc1be82ef7b6f4672c0b1677efbfb8b074
Service nicknames are represented by `HsNickname`, so let's
rename `HsClientSpecifier` to `HsClientNickname`.
Upgrade to strum 0.262024-01-30T17:48:00ZNick Mathewsonnickm@torproject.org2024-01-30T17:48:00Zurn:sha1:da83315bef0d1b7bc20f6760ec7e6e0fb0169a97