mirrors/arti.git/crates/tor-rtmock/Cargo.toml, branch arti-v1.1.12mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.122024-01-09T13:11:17ZPatchlevel version bumps in preparation for 1.1.12.2024-01-09T13:11:17ZNick Mathewsonnickm@torproject.org2024-01-09T13:07:43Zurn:sha1:ef150707800e7aba78948f0b5dc5a2dcefaf62b6
This crate doesn't have a meaningful public API, so it just gets a patchlevel bump:
arti
These crates had nonbreaking changes, and get a patchlevel bump:
tor-rtcompat
fs-mistrust
tor-llcrypto
tor-cert
Breaking version bumps in preparation for 1.1.12.2024-01-09T13:07:43ZNick Mathewsonnickm@torproject.org2024-01-09T13:07:43Zurn:sha1:565b44dc8e0a40d82b2eb32869b04b807b19cd9c
These crates have breaking changes on their own:
tor-error
tor-netdoc
tor-dirmgr
tor-keymgr
Because of the breaking change in tor-error, and the fact that
basically every crate publicly depends on tor-error (by implementing
ErrorKind), we need to call this a breaking change on all of the
following:
tor-config
tor-geoip
tor-rtmock
tor-log-ratelim
tor-rpcbase
tor-bytes
tor-hscrypto
tor-socksproto
tor-cell
tor-proto
tor-netdoc
tor-netdir
tor-persist
tor-chanmgr
tor-ptmgr
tor-guardmgr
tor-circmgr
tor-dirclient
tor-dirmgr
tor-keymgr
tor-hsclient
tor-hsservice
tor-hsrproxy
arti-client
arti-rpcserver
arti-config
arti-hyper
arti-testing
Update to derive-adhoc 0.82024-01-02T16:17:19ZIan Jacksonijackson@chiark.greenend.org.uk2024-01-02T15:58:05Zurn:sha1:2add0c7c26b576285d871d01e031f58f94039f14
As recommended in the d-a changelog, I'm not calling this a breaking
change to our APIs.
Bump patchlevel versions in preparation for release2023-12-04T16:33:36ZNick Mathewsonnickm@torproject.org2023-12-04T16:22:58Zurn:sha1:606905bd1fa3307a77a02463fa863f4c2b7cb890
These crates had backward-compatible changes, and get a patchlevel
bump only:
fs-mistrust
tor-error
tor-config
tor-rtcompat
tor-rtmock
This crate exposes no non-CLI APIs, and gets a patchlevel bump only:
arti
In every crate, change rust-version to 1.70.2023-11-28T16:35:51ZNick Mathewsonnickm@torproject.org2023-11-28T16:35:51Zurn:sha1:1b53c4ca3059fc395c98e2e6d0eb3b58f37c8ec1Upgrade to itertools 0.12.02023-11-15T14:53:42ZNick Mathewsonnickm@torproject.org2023-11-15T14:53:42Zurn:sha1:b658983309874f2122bbe59471b00848283f1ed0Patch version bumps in crates without breaking changes2023-10-31T13:12:35ZNick Mathewsonnickm@torproject.org2023-10-31T13:00:42Zurn:sha1:537d98a12eedf5604fe28183ec603dd3609bb070
```
These crates have new APIs:
tor-async-utils ADDED
tor-config ADDED
tor-hscrypto ADDED
tor-netdoc ADDED, plus BREAKING-experimental.
These crates have patch-level changes only:
tor-netdir (bugfix only). (re-exposes netdoc)
arti-rpcserver (tweaks only, uses nothing that broke.)
arti 1.1.10, no stable public APIs.
```
Minor version bumps in crates with breaking changes.2023-10-31T13:12:35ZNick Mathewsonnickm@torproject.org2023-10-31T12:54:00Zurn:sha1:4460d8b3a5f801db2b20ca0e83dadd0bc8ccf5da
```
tor-basic-utils BREAKING
tor-rtmock BREAKING.
tor-cert BREAKING
tor-cell BREAKING
tor-proto BREAKING: re-exposes cell. (Also BREAKING-experimental)
tor-chanmgr BREAKING: Re-exposes proto.
tor-ptmgr BREAKING: re-exposes tor-chanmgr
tor-guardmgr BREAKING: re-exposes proto. (Only for ClockSkew I think?)
tor-circmgr BREAKING: re-exposes proto
tor-dirclient BREAKING
tor-hsclient BREAKING, re-exposes proto.
tor-hsservice BREAKING, re-exposes proto.
tor-hsrproxy BREAKING
arti-client BREAKING: re-exposes proto.
arti-hyper: BREAKING, re-exposes arti-client.
tor-dirmgr Let's assume BREAKING, very high-level.
tor-keymgr BREAKING, but experimental.
```
Run "fixup-features" in preparation for release this week.2023-10-29T12:25:28ZNick Mathewsonnickm@torproject.org2023-10-29T12:25:28Zurn:sha1:d804f1a2bc43545db5d2cce379dbc1bad7728176oneshot: Use veneer in tor-rtmock2023-10-11T15:19:21ZIan Jacksonijackson@chiark.greenend.org.uk2023-10-11T14:01:34Zurn:sha1:87729eca8912a64cc0ad1af1f7bf75a39c87dabe