mirrors/arti.git/crates/tor-cert, branch arti-v2.5.1mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v2.5.12026-08-03T19:31:55ZBump versions for tor-* and arti-* crates2026-08-03T19:31:55ZSteven Engleropara@torproject.org2026-08-03T19:31:52Zurn:sha1:8c8f2375bb0402467fd0e7bc8b2547055d2f75f4
```bash
readarray -t bump < <(maint/list-crates | grep -P '^tor-|^arti-')
for crate in "${bump[@]}"; do cargo set-version --bump minor -p "${crate}"; done
```
tor-checkable: Rename `TimeBound::check_valid_*` to `if_valid_*`2026-07-23T10:13:34ZIan Jacksonijackson@chiark.greenend.org.uk2026-07-20T16:40:18Zurn:sha1:ca37f30a097696ce2ebd4e9945a4bdaebe086b31
I find these names confusing. To my mind "check" implies a function
returning `Result<(), _>`.
Some other APIs use `unwrap` here but I think `if` is good.
tor-checkable: TimeBound: Make wrapped type an associated type2026-07-23T10:13:34ZIan Jacksonijackson@chiark.greenend.org.uk2026-07-20T12:00:15Zurn:sha1:b16e7a5ac48daa3e2f94660bdf7c39f54e7c702c
It wouldn't make much sense for one concrete type to be unwrappable
variously as different inner types.
tor-checkable: TimeBound: Make is_valid_at a provided method2026-07-23T10:13:34ZIan Jacksonijackson@chiark.greenend.org.uk2026-07-16T15:30:15Zurn:sha1:9313f79335c2ba15e7e60bc6d97086c4c56ff30a
Now that we have `bounds()`, we can centralise this implementation and
delete the implementations.
I don't think it's necessary to provide an engineered safeguard
against downstreams overriding this method. Any existing implementors
of this trait will break because they must provide `.bounds()` now,
which is an opportunity to notice that the `is_valid_at` can be
deleted. But, if it is not deleted, nothing goes wrong.
tor-checkable: TimeBound: remove Error associated type2026-07-23T10:13:34ZIan Jacksonijackson@chiark.greenend.org.uk2026-07-16T15:19:05Zurn:sha1:726f97b2a2099eea34d804e0132cf742964af8b7
This was always TimeValidityError. And we want to rely on that so we
can do the validity checking more centrally.
tor-checkable: TimeBound: Add bounds accessor2026-07-23T10:13:34ZIan Jacksonijackson@chiark.greenend.org.uk2026-07-20T18:25:52Zurn:sha1:845f56aeedabfd44ec4573f872aeefa77cf72556
This makes a `TimeBound` much more convenient to work with, will allow
more centralisation.
This replaces temporary `bound` inherent method on `TimeRangeBound`.
Use new TimeRangeBound name throughout the tree2026-07-16T15:47:50ZIan Jacksonijackson@chiark.greenend.org.uk2026-07-16T14:35:45Zurn:sha1:92c26c4c07be73c91890ed3d7d4e53a06f26d0a1Use new TimeBound name throughout the tree2026-07-16T15:47:50ZIan Jacksonijackson@chiark.greenend.org.uk2026-07-16T14:32:14Zurn:sha1:5f57903ab4a8c280acf8a5bec274c50d5f544fd6add_warning: add reference to arti#25562026-07-15T17:56:49ZJim Newsomejnewsome@torproject.org2026-07-15T17:56:49Zurn:sha1:6d333d6e6f0bf4d75fdc81e8865e06f6537d5af6Removed unnecessary lint2026-07-15T17:16:51Zpryty26238962075+pryty26@users.noreply.github.com2026-07-15T17:07:59Zurn:sha1:d12e408c1d62f29e58647c91a2714c49e3004cc4
Removed unnecessary lint