<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-dirmgr/Cargo.toml, branch arti-v1.2.7</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.2.7</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.2.7'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2024-09-03T17:57:12Z</updated>
<entry>
<title>Bump all the unstable tor- and arti- crates to 0.22.0.</title>
<updated>2024-09-03T17:57:12Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2024-09-03T17:25:54Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=c3c266707f2fd361a447d922c5acfbb3938d88f2'/>
<id>urn:sha1:c3c266707f2fd361a447d922c5acfbb3938d88f2</id>
<content type='text'>
Done using:

```
for crate in $(./maint/list_crates  | rg '^(tor|arti-)'); do
    cargo set-version -p $crate 0.22.0
done
```
</content>
</entry>
<entry>
<title>oneshot-fused-workaround: Set the initial version to 0.1.0.</title>
<updated>2024-09-03T15:22:43Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2024-09-03T14:55:25Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=a88af5e93762a8cd95321a3adc31b2bc2ae3bd4d'/>
<id>urn:sha1:a88af5e93762a8cd95321a3adc31b2bc2ae3bd4d</id>
<content type='text'>
This is the first time we're publishing this, so let's start at 0.1.0.
</content>
</entry>
<entry>
<title>Fix formatting issues introduced by fixup-features.</title>
<updated>2024-09-03T10:00:30Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2024-09-03T09:21:55Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=dfe02110114be3f17e439bf99f776521fd044e15'/>
<id>urn:sha1:dfe02110114be3f17e439bf99f776521fd044e15</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Run fixup-features in preparation for release.</title>
<updated>2024-09-03T10:00:30Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2024-09-03T09:10:10Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=1eea611d14630c2901962e5cba408f2b7cf456fc'/>
<id>urn:sha1:1eea611d14630c2901962e5cba408f2b7cf456fc</id>
<content type='text'>
</content>
</entry>
<entry>
<title>extract tor_async_utils::oneshot into ::oneshot-fused-workaround</title>
<updated>2024-08-28T14:27:46Z</updated>
<author>
<name>Jim Newsome</name>
<email>jnewsome@torproject.org</email>
</author>
<published>2024-08-22T19:20:36Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=46f7f01092e6ac55e3e958dc3a2228b1d36e26a1'/>
<id>urn:sha1:46f7f01092e6ac55e3e958dc3a2228b1d36e26a1</id>
<content type='text'>
Having this in the `tor-async-utils` crate prevents us from doing both
of the following without introducing a circular dependency:

* using it in `tor-rtmock` (which we currently do, particularly in
  tests).
* using `tor-rtmock` to test things in `tor-async-utils`. We don't do
  this yet, but it is generally sensible to do so. In particular we
  want to move the `stream_peak` module there, which is currently tested
  with `tor-rtmock`.

Moving this into its own crate avoids this circular dependency.
</content>
</entry>
<entry>
<title>Don't need to tell docs.rs to enable `docsrs` cfg</title>
<updated>2024-08-02T15:11:20Z</updated>
<author>
<name>Kunal Mehta</name>
<email>legoktm@debian.org</email>
</author>
<published>2024-08-02T15:11:20Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=9efdcf72380628e7efe260ed209e0cd6d326bb7b'/>
<id>urn:sha1:9efdcf72380628e7efe260ed209e0cd6d326bb7b</id>
<content type='text'>
It now does it automatically, see
&lt;https://docs.rs/about/builds#detecting-docsrs&gt;.
</content>
</entry>
<entry>
<title>Bump versions for tor- and arti- crates to 0.21.0</title>
<updated>2024-08-01T15:09:32Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-08-01T15:09:32Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=5c2019c5e55a370877b92af67312714b7660847c'/>
<id>urn:sha1:5c2019c5e55a370877b92af67312714b7660847c</id>
<content type='text'>
This is the result of:

```
for crate in $( ./maint/list_crates  |grep '^\(tor\|arti-\)' ); do
    cargo set-version -p $crate 0.21.0
done
```
</content>
</entry>
<entry>
<title>Update versions of 0.x tor-* and arti-* crates</title>
<updated>2024-06-27T12:24:55Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2024-06-27T12:24:55Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=cb70cfc32b623cf4d55ae481218a810af04dfea4'/>
<id>urn:sha1:cb70cfc32b623cf4d55ae481218a810af04dfea4</id>
<content type='text'>
nailing-cargo -uE set-version -p arti-client 0.20.0
nailing-cargo -uE set-version -p arti-relay 0.20.0
nailing-cargo -uE set-version -p arti-rpcserver 0.20.0
nailing-cargo -uE set-version -p tor-async-utils 0.20.0
nailing-cargo -uE set-version -p tor-basic-utils 0.20.0
nailing-cargo -uE set-version -p tor-bytes 0.20.0
nailing-cargo -uE set-version -p tor-cell 0.20.0
nailing-cargo -uE set-version -p tor-cert 0.20.0
nailing-cargo -uE set-version -p tor-chanmgr 0.20.0
nailing-cargo -uE set-version -p tor-checkable 0.20.0
nailing-cargo -uE set-version -p tor-circmgr 0.20.0
nailing-cargo -uE set-version -p tor-config 0.20.0
nailing-cargo -uE set-version -p tor-consdiff 0.20.0
nailing-cargo -uE set-version -p tor-dirclient 0.20.0
nailing-cargo -uE set-version -p tor-dirmgr 0.20.0
nailing-cargo -uE set-version -p tor-error 0.20.0
nailing-cargo -uE set-version -p tor-geoip 0.20.0
nailing-cargo -uE set-version -p tor-guardmgr 0.20.0
nailing-cargo -uE set-version -p tor-hsclient 0.20.0
nailing-cargo -uE set-version -p tor-hscrypto 0.20.0
nailing-cargo -uE set-version -p tor-hsrproxy 0.20.0
nailing-cargo -uE set-version -p tor-hsservice 0.20.0
nailing-cargo -uE set-version -p tor-keymgr 0.20.0
nailing-cargo -uE set-version -p tor-linkspec 0.20.0
nailing-cargo -uE set-version -p tor-llcrypto 0.20.0
nailing-cargo -uE set-version -p tor-log-ratelim 0.20.0
nailing-cargo -uE set-version -p tor-memquota 0.20.0
nailing-cargo -uE set-version -p tor-netdir 0.20.0
nailing-cargo -uE set-version -p tor-netdoc 0.20.0
nailing-cargo -uE set-version -p tor-persist 0.20.0
nailing-cargo -uE set-version -p tor-proto 0.20.0
nailing-cargo -uE set-version -p tor-protover 0.20.0
nailing-cargo -uE set-version -p tor-ptmgr 0.20.0
nailing-cargo -uE set-version -p tor-relay-selection 0.20.0
nailing-cargo -uE set-version -p tor-rpcbase 0.20.0
nailing-cargo -uE set-version -p tor-rtcompat 0.20.0
nailing-cargo -uE set-version -p tor-rtmock 0.20.0
nailing-cargo -uE set-version -p tor-socksproto 0.20.0
nailing-cargo -uE set-version -p tor-units 0.20.0

Each of which runs a rune like
  cargo set-version --offline -p tor-units 0.20.0
</content>
</entry>
<entry>
<title>Update to itertools 0.13.0</title>
<updated>2024-06-25T13:43:30Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2024-06-25T13:40:57Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=775d9a3e9e94a6f70d467e2e0dddd32af24169bc'/>
<id>urn:sha1:775d9a3e9e94a6f70d467e2e0dddd32af24169bc</id>
<content type='text'>
No code changes needed.

Precisely
  nailing-cargo -Eu upgrade --incompatible -p itertools
</content>
</entry>
<entry>
<title>Require strum 0.26.3</title>
<updated>2024-06-25T13:43:07Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2024-06-25T13:42:19Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=d38f58429fae471d46952ed8921b30b2914ed33e'/>
<id>urn:sha1:d38f58429fae471d46952ed8921b30b2914ed33e</id>
<content type='text'>
We're about to update to iterools 0.13.0.  We must therefore have a
version of strum which is not affected by
   https://github.com/Peternator7/strum/issues/358

Precisely
  git-grep -l '^strum' | xargs perl -i~ -pe 's{"0\.26"}{"0.26.3"}'

No changes to lockfile - we're already using 0.26.3, except perhaps in
the minimal versions test.
</content>
</entry>
</feed>
