mirrors/arti.git/crates/tor-rpc-connect/Cargo.toml, branch arti-v1.3.1mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.3.12024-12-02T15:41:21ZBump all the unstable tor- and arti- crates to 0.25.0.2024-12-02T15:41:21ZGabriela Moldovangabi@torproject.org2024-12-02T15:39:29Zurn:sha1:e29e7a9aab4312af6a35818cb01676376d888e49
Done using:
```
for crate in $(./maint/list_crates | rg '^(tor|arti-)'); do
cargo set-version -p $crate 0.25.0
done
```
Bump the versions of the non-{arti-,tor-} crates.2024-12-02T15:41:21ZGabriela Moldovangabi@torproject.org2024-12-02T15:32:52Zurn:sha1:158ff2d2c0ef59ce6cdf5e8d6fe499b50e762002
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):
```
maint/changed_crates -v "arti-v$LAST_VERSION" 2>&1 >/dev/null | grep -i "no change" | grep -v '\(tor\|arti\)-'
oneshot-fused-workaround: No change.
test-temp-dir: No change.
caret: No change.
```
* crates that only have non-functional changes (bump the patch version):
- slotmap-careful
- fslock-guard
- hashx
- equix
- fs-mistrust
- safelog
- retry-error
* crates where APIs were broken (bump minor):
None
The bumps from this commit were created using this script:
```
PATCH="
slotmap-careful
fslock-guard
hashx
equix
fs-mistrust
safelog
retry-error
"
for crate in $PATCH; do
cargo set-version --bump patch -p $crate;
done
```
Fix several Cargo.tomls to satisfy cargo-sort.2024-12-02T10:45:24ZGabriela Moldovangabi@torproject.org2024-12-02T10:45:09Zurn:sha1:338bafc206ae76a8ff847e26c55f84539c8247dfRun fixup-features in preparation for release (fmt).2024-12-02T10:21:22ZGabriela Moldovangabi@torproject.org2024-12-02T10:21:22Zurn:sha1:79ebfca2db4b631404329c4d25a91296eccaf839Run fixup-features in preparation for release.2024-12-02T10:18:10ZGabriela Moldovangabi@torproject.org2024-12-02T10:18:10Zurn:sha1:33ee39924dbffdd3f8686b1cf0420782b9675112tor-rpc-connect: Bump thiserror to 2.2024-11-28T14:44:12ZGabriela Moldovangabi@torproject.org2024-11-28T14:42:15Zurn:sha1:436579ae0c5c76a90e7c14e0f5fa3d3a7cd0b099connect points: Remember original string addresses2024-11-19T22:00:53ZNick Mathewsonnickm@torproject.org2024-11-05T14:19:15Zurn:sha1:8664faead874f77b114134730420a469444204ae
The cookie authentication protocol will need these.
rpc-connect: Types for cookie authentication.2024-11-19T22:00:53ZNick Mathewsonnickm@torproject.org2024-11-04T15:12:49Zurn:sha1:a5c4c3c748d89ac4c5e1648f619d3345c6f1ad92
(Cookie authentication is described in rpc-cookie-sketch.md)
RPC connect points: Facility to load from files.2024-11-19T22:00:53ZNick Mathewsonnickm@torproject.org2024-11-02T16:22:07Zurn:sha1:51331a80d88c4a52167ca6bcccc5e10d11cffc48tor-connect-point: new crate to manage RPC connect points2024-11-19T19:33:46ZNick Mathewsonnickm@torproject.org2024-10-31T12:55:17Zurn:sha1:2835f79f2e2d03b63cb8f27170eec789ca51f223
See doc/dev/rpc-book/src/rpc-connect-sketch.md for details.