mirrors/arti.git/crates/retry-error, branch arti-v1.5.0mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.5.02025-08-28T16:28:38ZBump the minor version of every published crate except for `arti`.2025-08-28T16:28:38ZNick Mathewsonnickm@torproject.org2025-08-28T16:28:38Zurn:sha1:27d2e61733c617985284870002ded86dfb3b6cab
Per policy, we bump the minor version of every tor-*, arti-* crate
on each release.
We have updated our MSRV, so we're treating this as a breaking
change for our non-(arti/tor)-prefixed crates too.
Switch Cargo.toml files to edition 2024.2025-08-07T15:28:36ZNick Mathewsonnickm@torproject.org2025-08-06T01:19:58Zurn:sha1:77b0de43b8c67cdb81befe0680a3df43b6ad37bc
First, run
```
git grep -l "^edition =" |
xargs perl -i -pe 's/^edition *=.*/edition = "2024"/;'
```
Second, manually verify that all Cargo.toml files have changed,
and nothing else has changed.
Third, run cargo fmt again.
Update code for Edition 20242025-08-07T15:28:31ZNick Mathewsonnickm@torproject.org2025-08-07T12:44:47Zurn:sha1:0453fb4be8cf618b94230812957ce1db1afe74bd
1. Run cargo fix --edition
2. Selectively revert the "if let"->"match" changes.
These changes are meant to protect us from the lifetime changes
for "if let" bindings in Rust 2024.
But we're not actually relying on the old lifetime rules
anywhere, and the match syntax here is quite ugly.
3. Automatically revert `$pat:expr_2021` to `$pat:expr`.
(We don't actually want to restrict the expression syntax
that our macros accept).
Done with
`git grep -l expr_2021 | xargs perl -i -pe 's/expr_2021/expr/g;'`
4. Run cargo fmt.
Set MSRV to 1.85.2025-08-05T19:47:14ZNick Mathewsonnickm@torproject.org2025-08-05T19:47:14Zurn:sha1:b96d16a9ff7ee01a4356ffaf32a3bc11086ebe88Bump the versions of the non-{arti-,tor-} crates.2025-07-07T17:41:41ZGabriela Moldovangabi@torproject.org2025-07-07T17:24:35Zurn:sha1:c69083de50fb19331eba474ec6d1a3e5893274a3
The non-{arti-,tor-} crates are:
```
./maint/list_crates | rg -v '^(tor|arti)'
oneshot-fused-workaround
slotmap-careful
test-temp-dir
fslock-guard
hashx
equix
caret
fs-mistrust
safelog
retry-error
```
We split them in the following categories:
* crates with no changes (no version bumps): None
```
maint/changed_crates -v "arti-v$LAST_VERSION" 2>&1 >/dev/null | grep -i "no change" | grep -v '\(tor\|arti\)-'
```
* crates that only have non-functional changes (bump the patch version):
- oneshot-fused-workaround
- slotmap-careful
- test-temp-dir
- fslock-guard
- hashx
- equix
- caret
- safelog
- retry-error
* crates where APIs were broken (bump minor):
- fs-mistrust (the implicit once_cell feature was removed)
The bumps from this commit were created using this script:
```
PATCH="
oneshot-fused-workaround
slotmap-careful
test-temp-dir
fslock-guard
hashx
equix
caret
safelog
retry-error
"
for crate in $PATCH; do
cargo set-version --bump patch -p $crate;
done
MINOR="
fs-mistrust
"
for crate in $MINOR; do
cargo set-version --bump minor -p $crate;
done
```
Temporarily suppress mismatched_lifetime_syntaxes.2025-07-07T15:50:04ZGabriela Moldovangabi@torproject.org2025-07-07T15:50:04Zurn:sha1:a11b611466a5a73f5e06a0aabd17284a57d12fe3
See #2060.
release: Bump creates with non-functional changes.2025-06-05T10:22:16ZAlexander Hansen Færøyahf@torproject.org2025-06-05T10:22:16Zurn:sha1:90d059213e03127ad748c43974925ff73fe5f61d
caret, hashx, oneshot-fused-workaround, retry-error, safelog,
slotmap-careful, and test-temp-dir all only had the change from
88e911acd4bb70bf1da0fc71d77b51cb6abde478 where we bump the rust-version
to 1.83.
Done using:
./maint/bump_nodep retry-error safelog caret hashx test-temp-dir \
slotmap-careful oneshot-fused-workaround
All crates: bump rust-version to 1.83.2025-05-13T18:46:28ZNick Mathewsonnickm@torproject.org2025-05-13T18:46:28Zurn:sha1:88e911acd4bb70bf1da0fc71d77b51cb6abde478Bump patchlevel for safelog, retry-error, test-temp-dir.2025-03-03T13:13:04ZNick Mathewsonnickm@torproject.org2025-03-03T13:13:04Zurn:sha1:1639f2e07995aeb4ee9c7e2a633ce237afe5d621
These crates have upgraded to a newer derive_more,
and have had no other changes.
Upgrade to derive_more 22025-02-26T18:06:37ZNick Mathewsonnickm@torproject.org2025-02-26T17:50:42Zurn:sha1:d4dfbd6e1af1935af8cc4b83831891165da6af51
This took a little refactoring, since derive_more::Foo
no longer re-exports std::ops::Foo.