| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
```bash
readarray -t bump < <(maint/list-crates | grep -P '^tor-|^arti-')
for crate in "${bump[@]}"; do cargo set-version --bump minor -p "${crate}"; done
```
|
| |
|
|
|
|
|
|
|
|
| |
I'm not actually sure what I did here. I was getting a lot of confusing
results from 'cargo sort' and 'maint/cargo-sort', so I ran a bunch of
commands until 'maint/cargo-sort' was okay. ('maint/cargo-sort' still
shows some errors, but not in arti-dirauth anymore.)
But as long as the 'maint/cargo-sort' in CI is okay with the changes,
then I think it's fine.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
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'
|
| |
|
|
|
| |
Apparently these crate creations were outstanding when the workspace's
edition was increased.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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
```
|
| | |
|
| | |
|
| | |
|
| |
|
