mirrors/arti.git/crates/tor-error/Cargo.toml, branch arti-v1.2.0mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.2.02024-02-05T16:20:43ZBump patch versions (without dependency updates)2024-02-05T16:20:43ZIan Jacksonijackson@chiark.greenend.org.uk2024-02-05T16:17:20Zurn:sha1:e791dfd4e65849c6a45c6adc79a9dc312c7cfeff
These crates have had trivial changes which have no implications for
their dependencies:
safelog
tor-error
tor-config
Require tracing-test 0.2.42024-01-31T12:54:09ZIan Jacksonijackson@chiark.greenend.org.uk2024-01-31T11:19:36Zurn:sha1:475bbafb821818d773bb0375a036dc2c46f259fa
Apparently we need
https://github.com/dbrgn/tracing-test/pull/17
too.
Require tracing-test 0.2.22024-01-31T12:54:09ZIan Jacksonijackson@chiark.greenend.org.uk2024-01-31T11:01:30Zurn:sha1:b3276f7ec8401cfd398f740561f60952c6dcb83e
We need this bugfix
https://github.com/dbrgn/tracing-test/pull/15
for `#[traced_test]` when `Result` is redefined.
Fixes the tests with minimal-versions.
Upgrade to strum 0.262024-01-30T17:48:00ZNick Mathewsonnickm@torproject.org2024-01-30T17:48:00Zurn:sha1:da83315bef0d1b7bc20f6760ec7e6e0fb0169a97Breaking 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
tor-error: tests: Demonstrate warn_report on bare error and anyhow2023-12-12T13:14:22ZIan Jacksonijackson@chiark.greenend.org.uk2023-12-12T12:29:50Zurn:sha1:3de9c7e3b4d22d4c9d860457d1525a124430314fBump 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:1b53c4ca3059fc395c98e2e6d0eb3b58f37c8ec1Update patchlevel for crates with nontrivial changes.2023-09-05T16:22:19ZNick Mathewsonnickm@torproject.org2023-09-05T16:22:19Zurn:sha1:e251baa9a77415f3c605ff462a8ac0b3fa37660a
These are:
```
hashx
equix
tor-async-utils
tor-error
tor-config
tor-rtmock
tor-llcrypto
tor-bytes
tor-hscrypto
tor-hspow
tor-cert
tor-linkspec
tor-cell
tor-proto
tor-netdoc
tor-netdir
tor-chanmgr
tor-guardmgr
tor-dirmgr
tor-keymgr
tor-hsclient
tor-hsservice
arti-client
arti
```
tor-error, arti: Bump backtrace to 0.3.68.2023-08-15T15:34:31ZGabriela Moldovangabi@torproject.org2023-08-15T15:34:31Zurn:sha1:31645f4f373e821482b95ee4b9e1bd5856ed76aa
Previously we were using backtrace 0.3.39, which has a [bug] that causes
it to segault in some circumstances. I experienced this bug while trying
to fix the minimal-versions build in !1508.
[bug]: https://github.com/rust-lang/backtrace-rs/issues/267