<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-rpcbase, branch arti-v2.5.0</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v2.5.0</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v2.5.0'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2026-06-30T13:42:13Z</updated>
<entry>
<title>Version bumps for 2.5.0</title>
<updated>2026-06-30T13:42:13Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2026-06-30T13:42:13Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=245b03f5a48b4e58f8c84f072920160fc87be500'/>
<id>urn:sha1:245b03f5a48b4e58f8c84f072920160fc87be500</id>
<content type='text'>
Closes #2617.

We've lucked out this time, and it turns out that every one of our
published crates gets a minor bump.  So this was generated with:

```
for cr in $(./maint/list-crates); do
   cargo set-version -p $cr --bump minor
done
```
</content>
</entry>
<entry>
<title>Bump MSRV to 1.91</title>
<updated>2026-06-15T13:18:11Z</updated>
<author>
<name>Clara Engler</name>
<email>cve@cve.cx</email>
</author>
<published>2026-06-15T12:59:25Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=e93e0e2f9f42f526a8e1aa64e6ea659ef31dd800'/>
<id>urn:sha1:e93e0e2f9f42f526a8e1aa64e6ea659ef31dd800</id>
<content type='text'>
This commit bumps the MSRV to 1.91 which was released on 2025-10-30.

The Cargo.toml files were updated as follows:
```sh
git ls-files | \
    grep ".*Cargo\.toml$" | \
    xargs sed -i '' 's/^rust-version = "1\.89"$/rust-version = "1\.91"/g'
```

The following files were updated manually:
```
	modified:   .gitlab-ci.yml
	modified:   README.md
	modified:   flake.nix
	modified:   maint/docker-android/Dockerfile
```
</content>
</entry>
<entry>
<title>Merge branch 'clippy-string-slice' into 'main'</title>
<updated>2026-06-10T12:44:52Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2026-06-10T12:44:52Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=0400288b1f65ca489a6d27f357331618e132eb1c'/>
<id>urn:sha1:0400288b1f65ca489a6d27f357331618e132eb1c</id>
<content type='text'>
Lint for clippy::string_slice

See merge request tpo/core/arti!4086</content>
</entry>
<entry>
<title>maint: Run maint/add_warning to deny string slices</title>
<updated>2026-06-09T15:36:01Z</updated>
<author>
<name>Clara Engler</name>
<email>cve@cve.cx</email>
</author>
<published>2026-06-09T15:36:01Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=9f5752a77fb57052c06ead0eeae606831f1e8e97'/>
<id>urn:sha1:9f5752a77fb57052c06ead0eeae606831f1e8e97</id>
<content type='text'>
This commit executes maint/add_warning with the just added change to
deny string slices except in tests.

I recommend auditing this by checking out the previous commit followed
by running the script yourself and then verifying that the diff is
identical to this commit.

This commit makes cargo clippy fail.  We will add exceptions in the next
commit.
</content>
</entry>
<entry>
<title>Bump derive-deftly to 1.11.3</title>
<updated>2026-06-09T15:00:06Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2026-06-09T14:59:40Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=8d8fcae5af5c85e77ce7e5a1377314f607172c06'/>
<id>urn:sha1:8d8fcae5af5c85e77ce7e5a1377314f607172c06</id>
<content type='text'>
New beta semver policy means we should pin the patchlevel.
</content>
</entry>
<entry>
<title>Bump all the unstable tor- and arti- crates to 0.43.0</title>
<updated>2026-06-01T16:32:03Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2026-06-01T16:32:03Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=2100e7c8586af3616310d2bc18bbe971af77f1f1'/>
<id>urn:sha1:2100e7c8586af3616310d2bc18bbe971af77f1f1</id>
<content type='text'>
Done using:

```
for crate in $(./maint/list-crates  | rg '^(tor|arti-)'); do
    cargo set-version -p $crate 0.43.0
done
```
</content>
</entry>
<entry>
<title>release: Remove semver.md files.</title>
<updated>2026-05-06T22:00:43Z</updated>
<author>
<name>Wesley Aptekar-Cassels</name>
<email>me@wesleyac.com</email>
</author>
<published>2026-05-06T22:00:43Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=0601163d8ca11222e1abc5bef51a28321ff00acb'/>
<id>urn:sha1:0601163d8ca11222e1abc5bef51a28321ff00acb</id>
<content type='text'>
</content>
</entry>
<entry>
<title>release: Bump tor- and arti- crate versions.</title>
<updated>2026-05-06T16:59:22Z</updated>
<author>
<name>Wesley Aptekar-Cassels</name>
<email>me@wesleyac.com</email>
</author>
<published>2026-05-06T16:59:22Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=ff8102632670bb1f8d1fb84737ed49f32d3032a9'/>
<id>urn:sha1:ff8102632670bb1f8d1fb84737ed49f32d3032a9</id>
<content type='text'>
cargo set-version -p arti-client 0.42.0
cargo set-version -p arti-config 0.42.0
cargo set-version -p arti-relay 0.42.0
cargo set-version -p arti-rpc-client-core 0.42.0
cargo set-version -p arti-rpcserver 0.42.0
cargo set-version -p arti-testing 0.42.0
cargo set-version -p arti-ureq 0.42.0
cargo set-version -p tor-async-utils 0.42.0
cargo set-version -p tor-basic-utils 0.42.0
cargo set-version -p tor-bytes 0.42.0
cargo set-version -p tor-cell 0.42.0
cargo set-version -p tor-cert 0.42.0
cargo set-version -p tor-cert-x509 0.42.0
cargo set-version -p tor-chanmgr 0.42.0
cargo set-version -p tor-checkable 0.42.0
cargo set-version -p tor-circmgr 0.42.0
cargo set-version -p tor-config 0.42.0
cargo set-version -p tor-config-path 0.42.0
cargo set-version -p tor-consdiff 0.42.0
cargo set-version -p tor-dirclient 0.42.0
cargo set-version -p tor-dircommon 0.42.0
cargo set-version -p tor-dirmgr 0.42.0
cargo set-version -p tor-dirserver 0.42.0
cargo set-version -p tor-error 0.42.0
cargo set-version -p tor-events 0.42.0
cargo set-version -p tor-general-addr 0.42.0
cargo set-version -p tor-geoip 0.42.0
cargo set-version -p tor-guardmgr 0.42.0
cargo set-version -p tor-hsclient 0.42.0
cargo set-version -p tor-hscrypto 0.42.0
cargo set-version -p tor-hsrproxy 0.42.0
cargo set-version -p tor-hsservice 0.42.0
cargo set-version -p tor-key-forge 0.42.0
cargo set-version -p tor-keymgr 0.42.0
cargo set-version -p tor-linkspec 0.42.0
cargo set-version -p tor-llcrypto 0.42.0
cargo set-version -p tor-log-ratelim 0.42.0
cargo set-version -p tor-memquota 0.42.0
cargo set-version -p tor-memquota-cost 0.42.0
cargo set-version -p tor-netdir 0.42.0
cargo set-version -p tor-netdoc 0.42.0
cargo set-version -p tor-persist 0.42.0
cargo set-version -p tor-proto 0.42.0
cargo set-version -p tor-protover 0.42.0
cargo set-version -p tor-ptmgr 0.42.0
cargo set-version -p tor-relay-crypto 0.42.0
cargo set-version -p tor-relay-selection 0.42.0
cargo set-version -p tor-rpcbase 0.42.0
cargo set-version -p tor-rpc-connect 0.42.0
cargo set-version -p tor-rtcompat 0.42.0
cargo set-version -p tor-rtmock 0.42.0
cargo set-version -p tor-socksproto 0.42.0
cargo set-version -p tor-units 0.42.0
</content>
</entry>
<entry>
<title>Revert "rpc: Suppress a clippy false positive that appears with current beta"</title>
<updated>2026-05-04T14:17:54Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2026-05-04T14:14:02Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=23d6e9f74cf0f3055c79c6b688761259831390f6'/>
<id>urn:sha1:23d6e9f74cf0f3055c79c6b688761259831390f6</id>
<content type='text'>
This reverts commit 9447e48d0c698d51c75706d5efedcd6142c82f2a, which
told Clippy to ignore a warning that (I think) no longer occurs.
(Clippy was complaining that we were _naming_ a function in a
const-context that wasn't const-stable at our MSRV.  But it's fine
to _name_ a non-const function in that case: we just can't _call_
it.)

See https://github.com/rust-lang/rust-clippy/issues/15792 for more
info on the clippy bug.

AFAICT the warning no longer appears with current beta, nightly,
or stable versions.
</content>
</entry>
<entry>
<title>rpc: Adjust invoke_rpc_method API and related lookups.</title>
<updated>2026-04-13T19:25:24Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2026-04-13T17:26:54Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=6785f80fde8a2c0e1dea91d51ec0f4d36bdcb6bf'/>
<id>urn:sha1:6785f80fde8a2c0e1dea91d51ec0f4d36bdcb6bf</id>
<content type='text'>
The important thing here is that we need to look up the object
_after_ we invoke any non-dispatched methods, since the object might
be an expired weak reference.

This required some related changes to tests and error types.

Additionally, it required us to change the return value of
Context::remove, since we can remove objects that are not completely
present.
</content>
</entry>
</feed>
