<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-dirmgr, branch arti-v1.1.2</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.2</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.2'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2023-02-28T12:18:37Z</updated>
<entry>
<title>Follow-on patchlevel bumps for crates with changed dependencies</title>
<updated>2023-02-28T12:18:37Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-02-28T12:18:37Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=2c9f8e35479fb2b59bb51de3efb424b0b1df4a56'/>
<id>urn:sha1:2c9f8e35479fb2b59bb51de3efb424b0b1df4a56</id>
<content type='text'>
These crates didn't have any changes until now, when I bumped
the versions of some other crates they depend on:

tor-consdiff
arti-hyper
arti-bench
arti-testing
</content>
</entry>
<entry>
<title>Patchlevel bumps for remaining changed crates.</title>
<updated>2023-02-28T12:13:27Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-02-28T12:13:27Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=f41449d0bd9a2db5f72dd9941fb897e5cd9b922d'/>
<id>urn:sha1:f41449d0bd9a2db5f72dd9941fb897e5cd9b922d</id>
<content type='text'>
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
</content>
</entry>
<entry>
<title>Bump minor versions for significant breaking changes.</title>
<updated>2023-02-28T12:05:15Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-02-28T12:05:15Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=3e257a7cb57801329f013e7c1dc2d8c2dc598e47'/>
<id>urn:sha1:3e257a7cb57801329f013e7c1dc2d8c2dc598e47</id>
<content type='text'>
This includes tor-cell, tor-proto, and tor-netdir.
</content>
</entry>
<entry>
<title>tor-dirmgr: Work around an apparent regression in `time`.</title>
<updated>2023-02-17T19:36:19Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-02-17T19:24:31Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=2b515c8d257586f1cd6bc6c74a61ed0de60aab4f'/>
<id>urn:sha1:2b515c8d257586f1cd6bc6c74a61ed0de60aab4f</id>
<content type='text'>
Some code in our tests that worked fine with time 0.3.17 no
longer works with 0.3.19, despite the semver.

See https://github.com/time-rs/time/issues/552 for the upstream bug.
</content>
</entry>
<entry>
<title>tor-netdoc: Change fill_from_previous_netdir</title>
<updated>2023-02-09T12:56:18Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-02-01T13:15:33Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=f69d7f96ac40dda53a8f4f6c01557195faaeff7c'/>
<id>urn:sha1:f69d7f96ac40dda53a8f4f6c01557195faaeff7c</id>
<content type='text'>
* Remove the return value, which was not used anywhere.
  Also remove the code to calculate the return value.

* Take an Arc&lt;NetDir&gt; rather than a reference.  We are going to want
  this for HS support.  This has no overall effect on the lifetime of
  the4 Arc, which was owned at the one call site and then imediately
  dropped.

* Change the documentation to explain what the function's role is in
  the netdir API, rather than the fiddly details of what it actually
  does internally.  Relegate the latter to a code comment.
  (When we have HS, this will do more, or, at least, make further
  arrangements.)
</content>
</entry>
<entry>
<title>Merge branch 'logs' into 'main'</title>
<updated>2023-02-01T18:19:33Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-02-01T18:19:33Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=8ee04ac2037d2d07a171f62d72c246e2c066ac52'/>
<id>urn:sha1:8ee04ac2037d2d07a171f62d72c246e2c066ac52</id>
<content type='text'>
Report causes of errors

Closes #680

See merge request tpo/core/arti!997</content>
</entry>
<entry>
<title>Bump the patch version of every crate that had API additions</title>
<updated>2023-02-01T15:36:29Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-02-01T15:36:29Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=7c1b6a5a81e382be6210c7e2b0aae9695ad0bef4'/>
<id>urn:sha1:7c1b6a5a81e382be6210c7e2b0aae9695ad0bef4</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>Bump the patch-level version of crates with _minor_ changes.</title>
<updated>2023-02-01T15:23:58Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-02-01T15:23:58Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=66f594a4b6fac81137886be90a7bda3687923d48'/>
<id>urn:sha1:66f594a4b6fac81137886be90a7bda3687923d48</id>
<content type='text'>
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.)
</content>
</entry>
<entry>
<title>Use ErrorReport - run rustfmt</title>
<updated>2023-01-30T18:52:32Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-01-30T18:51:16Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=37edcd688a63cd91a4652720d7d9fb66cc7efab1'/>
<id>urn:sha1:37edcd688a63cd91a4652720d7d9fb66cc7efab1</id>
<content type='text'>
Split off for ease of review and possible rebase.
</content>
</entry>
<entry>
<title>Use ErrorReport's .report() for two errors in error! in bridgedesc.rs</title>
<updated>2023-01-30T18:52:32Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-01-30T18:48:29Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=aa7397bc0f43f67f42ed7f2e8dbe2ecdbf302058'/>
<id>urn:sha1:aa7397bc0f43f67f42ed7f2e8dbe2ecdbf302058</id>
<content type='text'>
No functional change, just using the new idiom.
</content>
</entry>
</feed>
