<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-rpcbase/Cargo.toml, branch arti-v1.2.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.2.0</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.2.0'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2024-02-05T16:13:29Z</updated>
<entry>
<title>Bump minor versions</title>
<updated>2024-02-05T16:13:29Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2024-02-05T16:13:29Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=af615d87e20d0984f493dfb8dda7b0654d8d7304'/>
<id>urn:sha1:af615d87e20d0984f493dfb8dda7b0654d8d7304</id>
<content type='text'>
Bump the minor version of these crates, and update the in-tree
dependencies.

Recently published as fresh crates, let's just assume there are
breaking changes:

   fslock-guard
   test-temp-dir

Breaking API change affecting many many downstream crates:

   tor-rtcompat

Downstream crates which we're (conservatively) assuming have
tor-rtcompat types in their APIs:

   tor-rtmock
   tor-log-ratelim
   tor-rpcbase
   tor-llcrypto
   tor-protover
   tor-bytes
   tor-hscrypto
   tor-hspow
   tor-socksproto
   tor-checkable
   tor-cert
   tor-linkspec
   tor-cell
   tor-proto
   tor-netdoc
   tor-consdiff
   tor-netdir
   tor-congestion
   tor-persist
   tor-chanmgr
   tor-ptmgr
   tor-guardmgr
   tor-circmgr
   tor-dirclient
   tor-dirmgr
   tor-keymgr
   tor-hsclient
   tor-hsservice
   tor-hsrproxy
   arti-client
   arti-rpcserver
   arti-config
   arti-hyper
   arti-bench
   arti-testing
</content>
</entry>
<entry>
<title>Bump to latest erased-serde.</title>
<updated>2024-01-09T15:31:29Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-01-09T15:31:29Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=2391e941e9443ed7c7bb54c1ad3904e068911438'/>
<id>urn:sha1:2391e941e9443ed7c7bb54c1ad3904e068911438</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Breaking version bumps in preparation for 1.1.12.</title>
<updated>2024-01-09T13:07:43Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-01-09T13:07:43Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=565b44dc8e0a40d82b2eb32869b04b807b19cd9c'/>
<id>urn:sha1:565b44dc8e0a40d82b2eb32869b04b807b19cd9c</id>
<content type='text'>
These crates have breaking changes on their own:

  tor-error
  tor-netdoc
  tor-dirmgr
  tor-keymgr

Because of the breaking change in tor-error, and the fact that
basically every crate publicly depends on tor-error (by implementing
ErrorKind), we need to call this a breaking change on all of the
following:

    tor-config
    tor-geoip
    tor-rtmock
    tor-log-ratelim
    tor-rpcbase
    tor-bytes
    tor-hscrypto
    tor-socksproto
    tor-cell
    tor-proto
    tor-netdoc
    tor-netdir
    tor-persist
    tor-chanmgr
    tor-ptmgr
    tor-guardmgr
    tor-circmgr
    tor-dirclient
    tor-dirmgr
    tor-keymgr
    tor-hsclient
    tor-hsservice
    tor-hsrproxy
    arti-client
    arti-rpcserver
    arti-config
    arti-hyper
    arti-testing
</content>
</entry>
<entry>
<title>Two more patchlevel bumps</title>
<updated>2023-12-04T16:37:56Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-12-04T16:37:56Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=c730cd00e5c131f62425be190579c7ce4748e11c'/>
<id>urn:sha1:c730cd00e5c131f62425be190579c7ce4748e11c</id>
<content type='text'>
These crates both depend on tor-error.  Since tor-error got a
patchlevel bump, they now depend on the new version, which means by
our rules that _they_ get a patchlevel bump themselves.

tor-geoip
tor-rpcbase
</content>
</entry>
<entry>
<title>Bump patchlevel versions in preparation for release</title>
<updated>2023-12-04T16:33:36Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-12-04T16:22:58Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=606905bd1fa3307a77a02463fa863f4c2b7cb890'/>
<id>urn:sha1:606905bd1fa3307a77a02463fa863f4c2b7cb890</id>
<content type='text'>
These crates had backward-compatible changes, and get a patchlevel
bump only:

fs-mistrust
tor-error
tor-config
tor-rtcompat
tor-rtmock

This crate exposes no non-CLI APIs, and gets a patchlevel bump only:

arti
</content>
</entry>
<entry>
<title>In every crate, change rust-version to 1.70.</title>
<updated>2023-11-28T16:35:51Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-11-28T16:35:51Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=1b53c4ca3059fc395c98e2e6d0eb3b58f37c8ec1'/>
<id>urn:sha1:1b53c4ca3059fc395c98e2e6d0eb3b58f37c8ec1</id>
<content type='text'>
</content>
</entry>
<entry>
<title>no-dependant bumps for crates with changed dependencies.</title>
<updated>2023-10-31T13:22:37Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-10-31T13:21:05Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=582502916d6aa0c6b3b11bb75dcf4246fa2fa947'/>
<id>urn:sha1:582502916d6aa0c6b3b11bb75dcf4246fa2fa947</id>
<content type='text'>
tor-rpcbase       patchlevel only, depends on async-utils.
tor-llcrypto      patchlevel only, depends on basic-utils.
tor-hspow         patchlevel only, depends on hscrypto.
tor-linkspec      patchlevel only, depends on basic-utils
</content>
</entry>
<entry>
<title>Patch version bumps in crates without breaking changes</title>
<updated>2023-10-31T13:12:35Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-10-31T13:00:42Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=537d98a12eedf5604fe28183ec603dd3609bb070'/>
<id>urn:sha1:537d98a12eedf5604fe28183ec603dd3609bb070</id>
<content type='text'>
```
These crates have new APIs:

tor-async-utils   ADDED
tor-config        ADDED
tor-hscrypto      ADDED
tor-netdoc        ADDED, plus BREAKING-experimental.

These crates have patch-level changes only:

tor-netdir        (bugfix only). (re-exposes netdoc)
arti-rpcserver    (tweaks only, uses nothing that broke.)
arti              1.1.10, no stable public APIs.

```
</content>
</entry>
<entry>
<title>Bump patchlevel (not dependents) on crates with trivial changes</title>
<updated>2023-09-05T16:25:24Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-09-05T16:25:24Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=a4badb9fdac5dd36ea173545f1ff417ccab1f49b'/>
<id>urn:sha1:a4badb9fdac5dd36ea173545f1ff417ccab1f49b</id>
<content type='text'>
This includes:

```
tor-basic-utils
caret
fs-mistrust
safelog
retry-error
tor-events
tor-units
tor-geoip
tor-rtcompat
tor-rpcbase
tor-protover
tor-socksproto
tor-checkable
tor-congestion
tor-persist
tor-circmgr
arti-rpcserver
arti-config
arti-hyper
arti-bench
arti-testing
tor-consdiff
```
</content>
</entry>
<entry>
<title>Update patchlevel for crates with nontrivial changes.</title>
<updated>2023-09-05T16:22:19Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-09-05T16:22:19Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=e251baa9a77415f3c605ff462a8ac0b3fa37660a'/>
<id>urn:sha1:e251baa9a77415f3c605ff462a8ac0b3fa37660a</id>
<content type='text'>
These are:

```
hashx
equix
tor-async-utils
tor-error
tor-config
tor-rtmock
tor-llcrypto
tor-bytes
tor-hscrypto
tor-hspow
tor-cert
tor-linkspec
tor-cell
tor-proto
tor-netdoc
tor-netdir
tor-chanmgr
tor-guardmgr
tor-dirmgr
tor-keymgr
tor-hsclient
tor-hsservice
arti-client

arti
```
</content>
</entry>
</feed>
