<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/arti/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 arti crate to 1.2.7</title>
<updated>2024-09-03T17:57:12Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2024-09-03T17:27:31Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=3af9510a3e574b978fb2cad06b06abab13743dcb'/>
<id>urn:sha1:3af9510a3e574b978fb2cad06b06abab13743dcb</id>
<content type='text'>
Done using:

```
cargo set-version --bump patch -p arti
```
</content>
</entry>
<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>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>arti: Remove the XXXXs added 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:14:45Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=dc9becb24e82c0f1eb9e15e8ced199211e329ff9'/>
<id>urn:sha1:dc9becb24e82c0f1eb9e15e8ced199211e329ff9</id>
<content type='text'>
The `restricted-discovery` feature is reachable from `experimental`.
</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>rpc: Use MockRuntime for set_proxy_info test.</title>
<updated>2024-08-28T13:00:59Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-08-28T12:45:59Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=dff8098fb935a2c81a6206eff14c9e09087dadaa'/>
<id>urn:sha1:dff8098fb935a2c81a6206eff14c9e09087dadaa</id>
<content type='text'>
</content>
</entry>
<entry>
<title>rpc: Try using postage::watch to initialize ProxyInfo.</title>
<updated>2024-08-28T13:00:31Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-08-27T17:16:15Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=ebbece794a2b11ff8d90af61be56a460d74255cd'/>
<id>urn:sha1:ebbece794a2b11ff8d90af61be56a460d74255cd</id>
<content type='text'>
(This is a bit trickier than I would like, but it ensures that we
never return a "not initialized yet" code.)
</content>
</entry>
<entry>
<title>Re-wrap a Cargo.toml.</title>
<updated>2024-08-28T13:00:31Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-08-27T16:24:42Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=d37f5b450f5bce1c2b40b65b1673500c28bfc933'/>
<id>urn:sha1:d37f5b450f5bce1c2b40b65b1673500c28bfc933</id>
<content type='text'>
</content>
</entry>
<entry>
<title>arti: Define a new ArtiRpcSession type.</title>
<updated>2024-08-28T13:00:31Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-08-22T12:46:32Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=657aa2e4d5dff83fadedec7a0be0e5413a27d8f3'/>
<id>urn:sha1:657aa2e4d5dff83fadedec7a0be0e5413a27d8f3</id>
<content type='text'>
This type exists in the `arti` crate.  It wraps and delegates to
`arti_rpcserver::RpcSession`.  Subsequent commits will use it to
expose information from the `arti` crate to the RPC system; right
now it does nothing.
</content>
</entry>
</feed>
