<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/arti, branch arti-v1.4.0</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.4.0</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.4.0'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2025-02-07T10:47:05Z</updated>
<entry>
<title>Bump minor version of fs-mistrust</title>
<updated>2025-02-07T10:47:05Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2025-02-06T18:24:38Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=d69fe98f10d469028e1cbbd3dff4eabd3ba3d816'/>
<id>urn:sha1:d69fe98f10d469028e1cbbd3dff4eabd3ba3d816</id>
<content type='text'>
Fixes #1841.
</content>
</entry>
<entry>
<title>Version bumps to 0.27.0</title>
<updated>2025-02-06T18:17:34Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2025-02-06T18:13:25Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=e590ba4d522b44ffc7adc0eea463309df2de12f3'/>
<id>urn:sha1:e590ba4d522b44ffc7adc0eea463309df2de12f3</id>
<content type='text'>
See Release.md.

maint/list_crates | grep -P '^tor-|^arti-' | xargs -n1 nailing-cargo -Eu set-version --bump minor -p

This completes the version bumps.

The report of changed crates, before I started the release work, is:

$ maint/changed_crates -v "arti-v$LAST_VERSION"
     oneshot-fused-workaround: No change.
     slotmap-careful: No change.
     test-temp-dir: No change.
     fslock-guard: No change.
     hashx: No change.
     equix: No change.
     tor-basic-utils: No change.
     caret: No change.
fs-mistrust
     safelog: No change.
     retry-error: No change.
tor-error
     tor-general-addr: No change.
     tor-geoip: No change.
tor-rtcompat
tor-rtmock
tor-async-utils
tor-config
tor-config-path
tor-rpc-connect
     tor-log-ratelim: No change.
tor-rpcbase
     tor-memquota: No change.
tor-units
     tor-llcrypto: No change.
     tor-protover: No change.
tor-bytes
     tor-checkable: No change.
tor-cert
tor-key-forge
     tor-hscrypto: No change.
     tor-socksproto: No change.
     tor-linkspec: No change.
     tor-cell: No change.
tor-proto
     tor-netdoc: No change.
     tor-consdiff: No change.
tor-netdir
     tor-relay-selection: No change.
tor-persist
tor-chanmgr
     tor-ptmgr: No change.
     tor-guardmgr: No change.
tor-circmgr
     tor-dirclient: No change.
     tor-dirmgr: No change.
tor-keymgr
tor-hsclient
tor-hsservice
     tor-hsrproxy: No change.
tor-relay-crypto
arti-client
arti-relay
arti-rpcserver
arti
arti-rpc-client-core
$
</content>
</entry>
<entry>
<title>Bump arti crate version to 1.4.0</title>
<updated>2025-02-06T18:17:34Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2025-02-06T18:08:38Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=823b9866d0f065f327d98063c6e6c5c564dab274'/>
<id>urn:sha1:823b9866d0f065f327d98063c6e6c5c564dab274</id>
<content type='text'>
And the in-tree dependencies.

cargo set-version --offline --bump minor -p fs-mistrust
</content>
</entry>
<entry>
<title>fs-mistrust: bump minor version, and in-tree deps</title>
<updated>2025-02-06T18:17:34Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2025-02-06T18:07:00Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=760400b3de12c5de121b6a7027a29ec78297c863'/>
<id>urn:sha1:760400b3de12c5de121b6a7027a29ec78297c863</id>
<content type='text'>
There are new features.

cargo set-version --offline --bump minor -p fs-mistrust

Actually, I have discovered by diffing that some methods now take
`&amp;self` where previously they took `self`.  This will need a further
bump to the fs-mistrust version and a fix to the changelog.

I will do that.  Filed blocker ticket #1841 for it.
</content>
</entry>
<entry>
<title>socks.rs: Update documentation; RpcDataStream has been renamed.</title>
<updated>2025-01-30T16:27:29Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-01-30T16:27:29Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=9f45c13ac0db1b10a0a95f566c62c87e6ce61128'/>
<id>urn:sha1:9f45c13ac0db1b10a0a95f566c62c87e6ce61128</id>
<content type='text'>
</content>
</entry>
<entry>
<title>rpc: Correct API documentation about optimism</title>
<updated>2025-01-30T15:08:17Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-01-30T15:03:04Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=fcb10040764db7204b637713b4166c4f57235257'/>
<id>urn:sha1:fcb10040764db7204b637713b4166c4f57235257</id>
<content type='text'>
Our documentation had dated to an older version of our RPC stream
code, where all streams were automatically optimistic.

But as explained, our use of "optimistic"ness in RPC stream code is
now purely internal, to make it possible to get an DataStreamCtrl.
This isn't user-visible in our rpc_conn_open_stream code.

Closes #1583
</content>
</entry>
<entry>
<title>Merge branch 'rpc-missing-dir' into 'main'</title>
<updated>2025-01-23T20:04:46Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-01-23T20:04:46Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=8c072fa31932449740fbf2731703f33c0d873dd5'/>
<id>urn:sha1:8c072fa31932449740fbf2731703f33c0d873dd5</id>
<content type='text'>
rpc: Tolerate NotFound on configured connect point directory.

See merge request tpo/core/arti!2735</content>
</entry>
<entry>
<title>connpts: Document behavior on nonexistent directory</title>
<updated>2025-01-23T18:20:37Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-01-23T18:20:37Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=22f9bb8f0de0b4d25a3b05ff806a026f50dfd211'/>
<id>urn:sha1:22f9bb8f0de0b4d25a3b05ff806a026f50dfd211</id>
<content type='text'>
</content>
</entry>
<entry>
<title>arti: Make Rpc argument unconditional when constructing socks proxy</title>
<updated>2025-01-23T17:25:41Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-01-23T17:18:09Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=49ce250eb1c2020b3cbaafa20086656491d98e14'/>
<id>urn:sha1:49ce250eb1c2020b3cbaafa20086656491d98e14</id>
<content type='text'>
Formerly this was a conditional method argument, which is a huge
antipattern.  Now it is unconditionally present, as `Option&lt;T&gt;` for
a type that is uninhabited when RPC isn't supported.
</content>
</entry>
<entry>
<title>arti::socks: Re-wrap a section.</title>
<updated>2025-01-23T17:06:07Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-01-23T17:06:07Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=4cc09c203276b09ce60f1245d429e51982977b9c'/>
<id>urn:sha1:4cc09c203276b09ce60f1245d429e51982977b9c</id>
<content type='text'>
rust-analyzer keeps re-wrapping this piece for me, even though
rustfmt doesn't complain.
</content>
</entry>
</feed>
