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: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-02-01T15:10:36Z Nick Mathewson nickm@torproject.org 2023-02-01T15:10:36Z urn:sha1:592d6bf8a3980cf383306e894215add2a5e9e6cd These crates have not had changes to their behavior; as such it is not necessary to bump their dependencies to require the new versions. 2023-01-27T13:28:02Z Nick Mathewson nickm@torproject.org 2023-01-27T13:01:45Z urn:sha1:a6dd92843edf2bd4c58de62a0d562921e4191ada This panics on error, and we're fine with a panic on misbehavior in tests. 2023-01-27T13:27:47Z Nick Mathewson nickm@torproject.org 2023-01-27T12:49:39Z urn:sha1:bf04641c6818cb2c87c6ed9cf463a5710f8919d2 This warning kind of snuck up on us! (See #748) For now, let's disable it. (I've cleaned it up in a couple of examples, since those are meant to be more idiomatic and user-facing.) Closes #748. 2022-12-12T18:00:30Z Ian Jackson ijackson@chiark.greenend.org.uk 2022-12-12T17:58:40Z urn:sha1:125a455bdcca841931f33f83f206e57637ae85c4 This is precisely the result of running the rune in maint/adhoc-add-lint-blocks. 2022-11-30T20:10:16Z Nick Mathewson nickm@torproject.org 2022-11-30T20:10:16Z urn:sha1:38bef96b99dbf17922dc601d4250abc0368b519f We made this job easy this time around: by incrementing our MSRV, we have forced ourselves to do at least a minor bump everywhere. 2022-11-10T15:57:33Z Nick Mathewson nickm@torproject.org 2022-11-07T19:18:02Z urn:sha1:936920b26e43447a010e249a9b5a5b9f69ca0da1 2022-11-03T15:06:02Z Nick Mathewson nickm@torproject.org 2022-11-03T15:06:02Z urn:sha1:932fe48eaf83f456eefd59475b4486d59966dec3 2022-10-12T14:29:04Z Ian Jackson ijackson@chiark.greenend.org.uk 2022-10-12T14:28:27Z urn:sha1:f84d8777db49f21ce6648dd244029531b370d5fd Apparently cargo fmt doesn't like these, which my perl rune didn't delete. This commit is precisely the result of `cargo fmt`.