mirrors/arti.git/crates/tor-checkable, branch arti-v2.5.0mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v2.5.02026-06-30T13:42:13ZVersion bumps for 2.5.02026-06-30T13:42:13ZNick Mathewsonnickm@torproject.org2026-06-30T13:42:13Zurn:sha1:245b03f5a48b4e58f8c84f072920160fc87be500
Closes #2617.
We've lucked out this time, and it turns out that every one of our
published crates gets a minor bump. So this was generated with:
```
for cr in $(./maint/list-crates); do
cargo set-version -p $cr --bump minor
done
```
tor-checkable: TODO for TimerangeBound from Timebound2026-06-23T14:44:55ZClara Englercve@cve.cx2026-06-23T12:26:37Zurn:sha1:3f5984d9f2ceefeb7406531d01f1259c15c87487Bump MSRV to 1.912026-06-15T13:18:11ZClara Englercve@cve.cx2026-06-15T12:59:25Zurn:sha1:e93e0e2f9f42f526a8e1aa64e6ea659ef31dd800
This commit bumps the MSRV to 1.91 which was released on 2025-10-30.
The Cargo.toml files were updated as follows:
```sh
git ls-files | \
grep ".*Cargo\.toml$" | \
xargs sed -i '' 's/^rust-version = "1\.89"$/rust-version = "1\.91"/g'
```
The following files were updated manually:
```
modified: .gitlab-ci.yml
modified: README.md
modified: flake.nix
modified: maint/docker-android/Dockerfile
```
tor-checkable: Specify Timebound inclusiveness in rustdoc2026-06-11T09:01:37ZClara Englercve@cve.cx2026-06-11T09:01:37Zurn:sha1:91a14182d48bc9faa9974ae3d2547cab56b20298
This commit updates Timebound's rustdoc to require inclusiveness when
checking the timeliness of a given object.
tor-checkable: TimerangeBound: test edge cases2026-06-10T14:42:10ZIan Jacksonijackson@chiark.greenend.org.uk2026-06-10T09:59:51Zurn:sha1:8dad38573005e533d78e0be581901590ffd5a1fbtor-checkable: TimeRangebound: document inclusivity2026-06-10T14:42:10ZIan Jacksonijackson@chiark.greenend.org.uk2026-06-10T08:54:30Zurn:sha1:b3ff5544712722bd954a8fac4b90f9d3694d4273tor-checkable: TimerangeBound: is_valid: Treat bounds as inclusive (fmt)2026-06-10T14:41:46ZIan Jacksonijackson@chiark.greenend.org.uk2026-06-04T14:11:40Zurn:sha1:da7de707ae1af8c5fbf1c583412da1aaf0918202tor-checkable: TimerangeBound: is_valid: Treat bounds as inclusive2026-06-10T14:41:46ZIan Jacksonijackson@chiark.greenend.org.uk2026-06-04T14:07:48Zurn:sha1:28434bbe2a372354824b8424743e3ce8738bef46
This makes more sense because:
* `start_bound` and `end_bound` return `Bound::Included`
* It doesn't make sense to say that a document isn't valid at
the very start of its validity period. (And we don't want a half-open range.)
* NotYetValid(0ns) and Expired(0ns) are rather nonsensical errors.
In real timeliness tests it will make no difference since the current
time is only equal to the bound for a nanosecond. But tests that like
to test corner cases might be affected, and possibly some synthetic
situations (where the document's own validity time start is used
somehow) might change.
maint: Run maint/add_warning to deny string slices2026-06-09T15:36:01ZClara Englercve@cve.cx2026-06-09T15:36:01Zurn:sha1:9f5752a77fb57052c06ead0eeae606831f1e8e97
This commit executes maint/add_warning with the just added change to
deny string slices except in tests.
I recommend auditing this by checking out the previous commit followed
by running the script yourself and then verifying that the diff is
identical to this commit.
This commit makes cargo clippy fail. We will add exceptions in the next
commit.
Bump all the unstable tor- and arti- crates to 0.43.02026-06-01T16:32:03ZGabriela Moldovangabi@torproject.org2026-06-01T16:32:03Zurn:sha1:2100e7c8586af3616310d2bc18bbe971af77f1f1
Done using:
```
for crate in $(./maint/list-crates | rg '^(tor|arti-)'); do
cargo set-version -p $crate 0.43.0
done
```