mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-1.2.1 2024-04-02T13:07:47Z 2024-04-02T13:07:47Z Nick Mathewson nickm@torproject.org 2024-04-02T13:07:47Z urn:sha1:cf257f7c24178946263ced1eeca0383db3e1732d These have all had backward-compatible changes. Generated with: ``` cargo set-version --bump patch -p fs-mistrust cargo set-version --bump patch -p test-temp-dir cargo set-version --bump patch -p fslock-guard cargo set-version --bump patch -p hashx cargo set-version --bump patch -p equix cargo set-version --bump patch -p caret cargo set-version --bump patch -p safelog cargo set-version --bump patch -p retry-error ``` 2024-03-05T11:13:39Z Ian Jackson iwj@torproject.org 2024-03-05T11:13:39Z urn:sha1:90873971d59d2a55b2f5ff4bd52a28459b564052 fslock-guard: Add unit tests See merge request tpo/core/arti!2013 2024-03-04T12:24:40Z Gabriela Moldovan gabi@torproject.org 2024-02-29T18:54:31Z urn:sha1:c1c81600935df2420981d881f08fe8e9e2642525 Functional changes were made, but no APIs were added or broken: ``` tor-events (async_broadcast 0.6.0 -> 0.7.0) tor-netdoc (signature 1 -> 2) tor-guardmgr arti-testing (config 0.13.4 -> 0.14.0) tor-persist (breaking changes gated behind experimental feature) fslock-guard (fix lockfile_has_path compilation on Windows) ``` Done with: ``` cargo set-version --bump patch -p tor-events cargo set-version --bump patch -p tor-netdoc cargo set-version --bump patch -p tor-guardmgr cargo set-version --bump patch -p arti-testing cargo set-version --bump patch -p tor-persist cargo set-version --bump patch -p fslock-guard ``` 2024-03-01T12:11:59Z Tobias Stoeckmann tobias@stoeckmann.org 2024-03-01T11:07:54Z urn:sha1:966b5721b860d61a7ed73c229b9e0d337fbfc1c4 This requires reordering of workspace members due to new internal dev-dependency. 2024-02-05T16:13:29Z Ian Jackson ijackson@chiark.greenend.org.uk 2024-02-05T16:13:29Z urn: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 2024-01-23T20:44:47Z Nick Mathewson nickm@torproject.org 2024-01-23T20:44:47Z urn:sha1:bd52d43779ed3a61d000bf16e96ed09ad924e141 2024-01-23T20:01:42Z Nick Mathewson nickm@torproject.org 2024-01-23T17:35:20Z urn:sha1:b9b8463973ef883a01e50d151fd0bc1104fe7156 2024-01-23T20:01:42Z Nick Mathewson nickm@torproject.org 2024-01-22T16:08:22Z urn:sha1:dae9c9afacc85eb6d9b791b5b1c924a9a25aba83 2024-01-21T21:51:25Z Nick Mathewson nickm@torproject.org 2024-01-21T21:46:27Z urn:sha1:70815226d086473152ec98a5ae8341ef4d067be3 This is not yet "correct", since it will rely on https://github.com/brunoczim/fslock/pull/15 (Conceivably, it might be better to make the `fslock` crate rm-safe.)