<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-dirclient/Cargo.toml, branch arti-v1.1.11</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.11</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.11'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2023-12-04T16:35:23Z</updated>
<entry>
<title>Bump minor versions in preparation for release</title>
<updated>2023-12-04T16:35:23Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-12-04T16:22:58Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=fba95e4b4708929ed09554632acd2e9f15e3c086'/>
<id>urn:sha1:fba95e4b4708929ed09554632acd2e9f15e3c086</id>
<content type='text'>
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
</content>
</entry>
<entry>
<title>Bump patchlevel versions in preparation for release</title>
<updated>2023-12-04T16:33:36Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-12-04T16:22:58Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=606905bd1fa3307a77a02463fa863f4c2b7cb890'/>
<id>urn:sha1:606905bd1fa3307a77a02463fa863f4c2b7cb890</id>
<content type='text'>
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
</content>
</entry>
<entry>
<title>Merge branch 'msrv-bump-1.70' into 'main'</title>
<updated>2023-11-30T14:40:45Z</updated>
<author>
<name>Ian Jackson</name>
<email>iwj@torproject.org</email>
</author>
<published>2023-11-30T14:40:45Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=7b23daffb5c2e903881c9b2d64a0bccc7b3f698e'/>
<id>urn:sha1:7b23daffb5c2e903881c9b2d64a0bccc7b3f698e</id>
<content type='text'>
Increase our MSRV to 1.70

See merge request tpo/core/arti!1773</content>
</entry>
<entry>
<title>dirclient: Upgrade to http 1.0</title>
<updated>2023-11-28T18:39:58Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-11-27T18:25:13Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=c5b386fb1009a1d91a830aeb67921c6057b98a1e'/>
<id>urn:sha1:c5b386fb1009a1d91a830aeb67921c6057b98a1e</id>
<content type='text'>
This is a breaking change, since dirclient::Error
exposes http::Error.
</content>
</entry>
<entry>
<title>In every crate, change rust-version to 1.70.</title>
<updated>2023-11-28T16:35:51Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-11-28T16:35:51Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=1b53c4ca3059fc395c98e2e6d0eb3b58f37c8ec1'/>
<id>urn:sha1:1b53c4ca3059fc395c98e2e6d0eb3b58f37c8ec1</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Upgrade to itertools 0.12.0</title>
<updated>2023-11-15T14:53:42Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-11-15T14:53:42Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=b658983309874f2122bbe59471b00848283f1ed0'/>
<id>urn:sha1:b658983309874f2122bbe59471b00848283f1ed0</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Patch version bumps in crates without breaking changes</title>
<updated>2023-10-31T13:12:35Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-10-31T13:00:42Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=537d98a12eedf5604fe28183ec603dd3609bb070'/>
<id>urn:sha1:537d98a12eedf5604fe28183ec603dd3609bb070</id>
<content type='text'>
```
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.

```
</content>
</entry>
<entry>
<title>Minor version bumps in crates with breaking changes.</title>
<updated>2023-10-31T13:12:35Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-10-31T12:54:00Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=4460d8b3a5f801db2b20ca0e83dadd0bc8ccf5da'/>
<id>urn:sha1:4460d8b3a5f801db2b20ca0e83dadd0bc8ccf5da</id>
<content type='text'>
```
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.
```
</content>
</entry>
<entry>
<title>Bump tor-dirclient patchlevel, since its dependency changed.</title>
<updated>2023-10-02T20:50:07Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-10-02T20:50:07Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=00e4405943498754e588cf060eb73250164a7c7a'/>
<id>urn:sha1:00e4405943498754e588cf060eb73250164a7c7a</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Minor-version bumps, for crates with breaking changes.</title>
<updated>2023-10-02T18:51:27Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-10-02T18:51:27Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=1c3c06d68fda250dff4039614aff0be765ff68e0'/>
<id>urn:sha1:1c3c06d68fda250dff4039614aff0be765ff68e0</id>
<content type='text'>
</content>
</entry>
</feed>
