mirrors/arti.git/Cargo.lock, branch arti-v1.2.6mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.2.62024-08-01T15:58:26ZMerge branch 'version-bumps-arti-v1.2.6' into 'main'2024-08-01T15:58:26ZNick Mathewsonnickm@torproject.org2024-08-01T15:58:26Zurn:sha1:55512ff45f643e6eac63fe4969b8d91e773d08fa
Version bumps for Arti 1.2.6
See merge request tpo/core/arti!2303Bump "arti" crate to 1.2.62024-08-01T15:15:11ZNick Mathewsonnickm@torproject.org2024-08-01T15:12:37Zurn:sha1:b12219b6dc58d4133f309e7f201abb503563aeff
Done with
```
cargo set-version --bump patch -p arti
```
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
```
Minor bumps on fslock-guard, fs-mistrust, equix2024-08-01T15:01:51ZNick Mathewsonnickm@torproject.org2024-08-01T15:01:51Zurn:sha1:3978b76e84a4c9fbcb51391dcf84a4e7920dfa06
No updates on their dependents, because:
fslock-guard (only tests have changed)
equix (only change is removal of a private constant)
fs-mistrust (documentation, formatting, and use of Path::try_exists in tests)
Unpin cc2024-08-01T14:35:33ZIan Jacksonijackson@chiark.greenend.org.uk2024-08-01T13:34:29Zurn:sha1:2b9440aba8ab8bc6cc573c48b71dd19c940fa785
The previous commit added a pinned dep on cc 1.0.93, which we don't
want.
See also !2231
Cargo.lock: Downgrade cc again2024-08-01T14:35:33ZIan Jacksonijackson@chiark.greenend.org.uk2024-08-01T13:26:46Zurn:sha1:77b8d777dbb032bf230a012aca59299242219440
Roughly the same as 32a45edb84a210eb9fa692f7f339b2a0b20cb1c6.
Add the line to arti's Cargo.toml for convenience for next time.
Run "cargo update" in preparation for release.2024-08-01T14:35:33ZNick Mathewsonnickm@torproject.org2024-08-01T12:12:12Zurn:sha1:a86bce1e358dc5e4ba1cda1a3da86c2da79f2fb8ffi: use void to omit unreachable "on invalid" blocks2024-07-31T17:54:16ZNick Mathewsonnickm@torproject.org2024-07-30T21:06:30Zurn:sha1:9c4c9e72d4cc76d58c577d15dbaea67507b108f3rpc: Initial core of an FFI interface.2024-07-31T17:54:16ZNick Mathewsonnickm@torproject.org2024-07-17T12:16:53Zurn:sha1:f6c1ffe05a4eaa61c30070a74716eb2f74710784
This only covers the absolute minimal API in order to launch a
connection and run simple requests, and it doesn't document anything
nearly well enough. Nonetheless I think it's good enough for an
initial review, to make sure that we've got the basics right (as
well as a general consensus on the error handling API, naming, and
so forth).
Update bytemuck to 1.16.3; previous version was yanked.2024-07-31T13:54:54ZNick Mathewsonnickm@torproject.org2024-07-31T13:54:54Zurn:sha1:6513bc8ca186f59e73ef112fef06e27c8fcf1ab8