mirrors/arti.git/crates/tor-hsrproxy/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
Run "fixup-features" in preparation for release.2024-01-08T18:30:34ZNick Mathewsonnickm@torproject.org2024-01-08T18:30:34Zurn:sha1:41782552e9602390cd6fbf79374dd4e2218ea119Update 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.
hsproxy: Add a rate-limited log for forwarding errors.2023-12-07T16:32:01ZNick Mathewsonnickm@torproject.org2023-12-07T16:30:06Zurn:sha1:428df5f77018d3ef7c5380bf4595618dca90d4e4hsrproxy: Reformat Cargo.toml.2023-12-07T16:32:01ZNick Mathewsonnickm@torproject.org2023-12-07T16:28:54Zurn:sha1:2287524fef9a50cd222715c3018c562dd75d829dupgrade to toml 0.8.82023-12-05T13:20:09ZNick Mathewsonnickm@torproject.org2023-12-05T13:20:09Zurn:sha1:30fa68ab489679afbbe707e8ac3d166ee50dda93Bump minor versions in preparation for release2023-12-04T16:35:23ZNick Mathewsonnickm@torproject.org2023-12-04T16:22:58Zurn:sha1:fba95e4b4708929ed09554632acd2e9f15e3c086
This crate is new, and gets a bump to 0.1.0.
tor-log-ratelim
This crate had a breaking change:
tor-persist
tor-llcrypto had a breaking change. These crates _are_
tor-llcrypto, or (transitively) depend on it. I am assuming that
they all re-expose something from it in a way that matters:
tor-llcrypto
tor-bytes
tor-hscrypto
tor-socksproto
tor-checkable
tor-cert
tor-linkspec
tor-cell
tor-proto
tor-netdoc
tor-consdiff
tor-netdir
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-hyper
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:1b53c4ca3059fc395c98e2e6d0eb3b58f37c8ec1