mirrors/arti.git/crates/tor-dircommon, branch arti-v2.5.1

Bump versions for tor-* and arti-* crates

2026-08-03T19:31:55Z

```bash readarray -t bump < <(maint/list-crates | grep -P '^tor-|^arti-') for crate in "${bump[@]}"; do cargo set-version --bump minor -p "${crate}"; done ```

Merge branch 'testdata-export' into 'main'

2026-07-27T09:59:22Z

tor-netdoc testdata-live: Export for the benefit of other crates See merge request tpo/core/arti!4229

Require derive-deftly 1.11.4

2026-07-23T10:53:57Z

We're about to *use* the fix that was in 1.11.4. We already updated the lockfile in !4228, so this is just Cargo.toml changes (which will prevent the minimal-versions tests failing when we change the code to rely on the fix). git-grep -l '^derive-deftly' |xargs perl -i~ -pe 's{\b\Q1.11.3\E\b}{1.11.4}g'

tor-checkable: TimeRangeBound: Rename extend_tolerance to extend_end_bound

2026-07-23T10:13:34Z

It was confusing that one of these functions had "which bound" mentioned in its name, but the other didn't. So add `end` and switch from `tolerance` to `bound` (see previous commit message). *This* commit should deal only in `extend_tolerance` and `end` and shouldn't touch `extend_start_bound` or `extend_pre_tolerance`.

tor-checkable: TimeRangeBound: Rename extend_pre_tolerance to extend_start_bound

2026-07-23T10:13:34Z

Although it is often used to apply a tolerance, it doesn't make sense to say that this is extending the "tolerance" of a `TimeRangeBound`. A `TimeRangeBound` doesn't have a tolerance, only bounds. Also we should be consistent in our terminology, and use `start` rather than `pre`. We'll rename the other method too. Doing them one at a time will makes it easier to spot any "pre/start" vs "/end" slips: *this* commit should deal only in `pre` and `start` and shouldn't touch `extend_tolerance`.

Use new TimeRangeBound name throughout the tree

2026-07-16T15:47:50Z

add_warning: add reference to arti#2556

2026-07-15T17:56:49Z

Removed unnecessary lint

2026-07-15T17:16:51Z

Removed unnecessary lint

Version bumps for 2.5.0

2026-06-30T13:42:13Z

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 ```

fallbackdir: Update list generated on June 25, 2026

2026-06-26T12:19:22Z

Signed-off-by: Tor CI Release