mirrors/arti.git/crates/tor-config/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
```
Run fixup-features in preparation for release.2024-09-03T10:00:30ZGabriela Moldovangabi@torproject.org2024-09-03T09:10:10Zurn:sha1:1eea611d14630c2901962e5cba408f2b7cf456fctor-config: Write tests for FileWatcher.2024-08-21T18:54:53ZGabriela Moldovangabi@torproject.org2024-08-19T16:52:25Zurn:sha1:d8475287fe413bcdabb15f192dd8b380632a82d3tor-config: Add getters for FileWatcher.2024-08-21T18:54:53ZGabriela Moldovangabi@torproject.org2024-08-19T14:06:46Zurn:sha1:4f17820a45167018728f9dbe25ae62bd42a64725
Sometimes it's useful to know what files/directories are being watched.
For example, the descriptor publisher needs to know in order to figure
out if it needs to update the watcher in response to changes in the
config.
tor-config: Make FileWatcher use an opaque channel type.2024-08-21T18:33:34ZGabriela Moldovangabi@torproject.org2024-08-15T17:25:14Zurn:sha1:1edd4392191742ac3be279775a8c3d6710f62b8a
The `FileWatcher` now uses a `postage::watch` channel under the hood.
tor-config: Give FileWatcherBuilder a handle to the runtime.2024-08-21T18:33:34ZGabriela Moldovangabi@torproject.org2024-08-15T15:27:40Zurn:sha1:de6f4d5f83b37939f606b0a60486896be8b5316e
The event handler will soon be made async, so we need a handle to the
runtime.