mirrors/arti.git/crates/retry-error, branch arti-v2.1.0mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v2.1.02026-03-02T17:36:23ZBump the versions of the non-{arti-,tor-} crates2026-03-02T17:36:23ZGabriela Moldovangabi@torproject.org2026-03-02T17:36:23Zurn:sha1:d45c09c8e808c90c4fcb5416fd52c3c138b4871a
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
futures-copy
```
Because this release bumps the MSRV, I am bumping the minor version of all of
them.
MINOR="
oneshot-fused-workaround
slotmap-careful
test-temp-dir
fslock-guard
hashx
equix
caret
fs-mistrust
safelog
retry-error
futures-copy
"
for crate in $MINOR; do
cargo set-version --bump minor -p $crate;
done
```
Merge branch 'ticket_2338' into 'main'2026-02-19T17:28:20ZNick Mathewsonnickm@torproject.org2026-02-19T17:28:20Zurn:sha1:61485a6893bf43deab6b2404a7d4e8ea0c722466
Use ErrorSources where appropriate to walk an error stack.
Closes #2338
See merge request tpo/core/arti!3685retry-error: Document why we don't need (and can't use) ErrorSources.2026-02-19T16:34:40ZNick Mathewsonnickm@torproject.org2026-02-16T15:41:59Zurn:sha1:d4883c3d333279c01a408495cdd70e33da5ade8bAllow clippy::collapsible_if to trigger2026-02-16T15:22:24ZGabriela Moldovangabi@torproject.org2026-02-09T11:49:02Zurn:sha1:ade1d59e8e44c93b6ee447b72a2948a9652ec44e
`clippy::collapsible_if` started triggering after bumping the MSRV to
1.88.
Since this triggers from a lot of places, and since there even are a
couple of instances where we explicitly allow `clippy::collapsible_ifs`,
I've opened #2342 for deciding what to do about it.
Bump MSRV from 1.86 to 1.892026-02-16T15:22:24ZGabriela Moldovangabi@torproject.org2026-02-09T11:29:39Zurn:sha1:c48a2ba6771016e7c57f02cfb99d62c3e5b34bc4
As agreed at our last team meeting.
See
https://gitlab.torproject.org/tpo/core/arti/#minimum-supported-rust-version
release: bump-nodep various crates.2026-02-02T17:04:00ZWesley Aptekar-Casselsme@wesleyac.com2026-02-02T16:59:35Zurn:sha1:fc21fcdaef0454044ee1ec93352c79f3be0df127
These were all only changed by a98faf72, which simply adds deny
statements for clippy::unused_async in various places.
It's not clear to me that we even need to bump these versions, but that
seems to be what our release documentation implies.
maint/add_warning: Run script to add new warning2026-01-27T18:05:36ZGabriela Moldovangabi@torproject.org2026-01-27T18:05:36Zurn:sha1:a98faf72eb06b47700faeeac5a8a0dd0fc29b584
This adds the lint to all our crates.
meta: Remove all semver.md files post-release2026-01-13T21:16:44ZClara Englercve@cve.cx2026-01-13T16:57:46Zurn:sha1:804d065fd01bda51231e959055de5f4139243e68
Fix the conflict in tor-netdoc/semver.md by hand, including the new
entries already landed since v1.9.0.
cargo: Bump all non arti/tor crates2026-01-12T12:44:12ZClara Englercve@cve.cx2026-01-12T12:40:27Zurn:sha1:7e5ed9f4b87e0dcdf6f2f4a8eaa77bbfda5f1b2a
This only includes retry-error which had a few functional additions in
December, thereby rasing the minor version as new features were added to
the public API.
Done using the following:
* Find all non arti, non tor crates.
* `ls -1 crates/ | grep -v "^tor-\|^arti"`
* Exclude the ones without changes.
* `maint/changed_crates -v "arti-v$LAST_VERSION" 2>&1 >/dev/null | grep -i "no change"`
* Look into each with changes.
* In this case only retry-error.
* Bump the minor because it had non-trivial changes.
chore: remove debug comments, use let-else2025-12-17T14:48:04ZNihal4218-nihalxkumar@gitlab.torproject.org2025-12-16T17:26:24Zurn:sha1:b9e695ec5ce67d7cb7664a026e802878c9d8a84f