mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=tor-llcrypto-v0.4.4 2023-03-31T12:30:14Z 2023-03-31T12:30:14Z Nick Mathewson nickm@torproject.org 2023-03-31T12:30:14Z urn:sha1:9ef115a7fb21fe7267d1d91ba7babac8e1b7542e These crates had no changes until just a moment ago. But since we updated the versions on some of their dependents, they have now changed themselves. Thus they get patchlevel bumps. ``` tor-rtmock tor-protover tor-socksproto tor-consdiff tor-chanmgr tor-dirclient tor-hsservice ``` 2023-03-31T12:28:06Z Nick Mathewson nickm@torproject.org 2023-03-31T12:28:06Z urn:sha1:e208fb15adb800ae41e472db464f984e9f4a4f5c These crates have had breaking changes. They are pre-1.0, so they get a minor bump. ``` tor-basic-utils tor-config ``` 2023-03-31T12:24:39Z Nick Mathewson nickm@torproject.org 2023-03-31T12:24:39Z urn:sha1:a81ab391ae9cc3b48cf08cf1b911f1b4cfa8be76 For these crates, the changes are nontrivial, so we _do_ bump the versions on which their dependent crates depend. Fortunately, since they are all pre-1.0, we don't need to distinguish semver-additions from other changes. (Except for arti, which _is_ post-1.0, but gets a patchlevel bump anyway.) These are unstable crates with breaking changes: ``` tor-hscrypto tor-hsclient ``` These have new or extended APIs: ``` safelog tor-bytes tor-cell tor-linkspec tor-llcrypto tor-proto tor-cert arti-client ``` These have new unstable APIs or features: ``` tor-netdoc tor-circmgr (also broke some unstable APIs) arti (is post-1.0) ``` These have bugfixes only: ``` caret tor-dirmgr ``` 2023-03-31T12:20:58Z Nick Mathewson nickm@torproject.org 2023-03-31T12:20:58Z urn:sha1:622c79aaa60e433712a7dc4d7b8900659fc78071 Their dependents are _not_ updated to a more recent version. These bumped the version of a dependency that they don't expose ``` tor-rtcompat fs-mistrust ``` This one had internal refactoring: ``` tor-netdir ``` These had trivial changes only: ``` tor-checkable tor-ptmgr tor-guardmgr arti-hyper arti-bench arti-testing ``` 2023-03-13T11:28:55Z Nick Mathewson nickm@torproject.org 2023-03-13T11:28:55Z urn:sha1:2ddaaafafb2149a88b42d2eec1f95f9c7a570365 Since we made the internals of the ptmgr protocol parser conditionally private, we need to tell Cargo to build the fuzzer with the `experimental-api` feature so that it can access them. 2023-02-28T12:13:27Z Nick Mathewson nickm@torproject.org 2023-02-28T12:13:27Z urn:sha1:f41449d0bd9a2db5f72dd9941fb897e5cd9b922d These crates have had small code changes, but no API additions: tor-config tor-socksproto tor-cert tor-chanmgr tor-ptmgr tor-guardmgr tor-circmgr tor-dirclient tor-dirmgr arti tor-hsservice tor-congestion These crates have had API extensions: fs-mistrust tor-llcrypto tor-bytes tor-checkable tor-linkspec tor-netdoc tor-persist arti-client 2023-02-01T18:19:33Z Nick Mathewson nickm@torproject.org 2023-02-01T18:19:33Z urn:sha1:8ee04ac2037d2d07a171f62d72c246e2c066ac52 Report causes of errors Closes #680 See merge request tpo/core/arti!997 2023-02-01T15:36:29Z Nick Mathewson nickm@torproject.org 2023-02-01T15:36:29Z urn:sha1:7c1b6a5a81e382be6210c7e2b0aae9695ad0bef4 These crates had API or behavior changes that may affect downstream crates. Fortunately, they're all version 0.x, and don't need minor bumps for this. 2023-02-01T15:23:58Z Nick Mathewson nickm@torproject.org 2023-02-01T15:23:58Z urn:sha1:66f594a4b6fac81137886be90a7bda3687923d48 These changes influence behavior, but not effect compatibility. (If I messed up, and any crate except for `arti` has non-breaking API changes, that's still fine, since they are all version 0.x.) 2023-01-30T18:52:32Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-01-30T18:51:16Z urn:sha1:37edcd688a63cd91a4652720d7d9fb66cc7efab1 Split off for ease of review and possible rebase.