<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-proto/Cargo.toml, branch arti-v1.1.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.1.7</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.7'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2023-08-01T14:57:55Z</updated>
<entry>
<title>Increment patchlevel versions of crates with minor changes</title>
<updated>2023-08-01T14:57:55Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-08-01T14:57:55Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=3acdf102c705314aec63679e97240bb7d981d1c8'/>
<id>urn:sha1:3acdf102c705314aec63679e97240bb7d981d1c8</id>
<content type='text'>
These crates are at version 0.x.y, so we don't need to distinguish
new-feature changes from other changes:

```
tor-basic-utils
fs-mistrust
tor-error
tor-geoip
tor-checkable
tor-linkspec
tor-netdoc
tor-netdir
tor-persist
tor-ptmgr
tor-hsservice
```

This crate has a breaking change, but only when the semver-breaking
feature `experimental-api` is enabled:

```
tor-config
```

This crate is at version 1.x.y, but has no new public APIs, and
therefore does not need a minor version bump:

```
arti
```
</content>
</entry>
<entry>
<title>Update minor versions on crates that have had breaking changes</title>
<updated>2023-08-01T14:51:25Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-08-01T14:51:25Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=6f2ae5960393b64c1d7615d2d523e050d3bebe5a'/>
<id>urn:sha1:6f2ae5960393b64c1d7615d2d523e050d3bebe5a</id>
<content type='text'>
These crates had first-order breaking changes:

```
retry-error
tor-keymgr
tor-proto
tor-hsclient
tor-rtmock
```

Additionally, these broke because they re-exposed RetryError:

```
tor-circmgr
```

Additionally, these broke because they may re-expose something from
tor-proto:

```
    arti-client
    tor-chanmgr
    tor-dirclient
    tor-dirmgr
    tor-guardmgr
```

Additionally, these broke for other fiddly reasons:

`tor-ptmgr` implements traits from tor-chanmgr, which has a breaking
change above.

`arti-hyper` exposes types from arti-client in its API.
</content>
</entry>
<entry>
<title>tor-proto conversations: Update a TODO</title>
<updated>2023-06-30T17:43:20Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-06-30T17:32:21Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=2a67468d27c27bf0fdd24d13f1788dad83e78f64'/>
<id>urn:sha1:2a67468d27c27bf0fdd24d13f1788dad83e78f64</id>
<content type='text'>
The feature name is wrong now.
</content>
</entry>
<entry>
<title>tor-proto conversation API: Return a Conversation</title>
<updated>2023-06-30T17:03:17Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-06-30T16:51:16Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=20f1e065b323351984fc2a5898ebe85b5ee534d1'/>
<id>urn:sha1:20f1e065b323351984fc2a5898ebe85b5ee534d1</id>
<content type='text'>
This is just a placeholder for now, but it'll be a thing you can send
more messages with.
</content>
</entry>
<entry>
<title>tor-proto conversation API: Rename to start_conversation_last_hop</title>
<updated>2023-06-30T17:02:56Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-06-30T16:51:02Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=2882e3a93e22a4acdfb93da8a2ca1e62a50141b2'/>
<id>urn:sha1:2882e3a93e22a4acdfb93da8a2ca1e62a50141b2</id>
<content type='text'>
Was send_control_message.
</content>
</entry>
<entry>
<title>Bump patchlevel versions on crates with smaller changes</title>
<updated>2023-06-30T12:42:21Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-06-30T12:42:21Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=de13a7319b7de5a336a70f128d1904954ed77f82'/>
<id>urn:sha1:de13a7319b7de5a336a70f128d1904954ed77f82</id>
<content type='text'>
Done with the commands below.

The following crates have had various changes, and should get a
patchlevel bump. Since they are pre-1.0, we do not need to
distinguish new APIs from other changes.

```
cargo set-version --bump patch -p arti-client
cargo set-version --bump patch -p safelog
cargo set-version --bump patch -p tor-bytes
cargo set-version --bump patch -p tor-cert
cargo set-version --bump patch -p tor-circmgr
cargo set-version --bump patch -p tor-config
cargo set-version --bump patch -p tor-consdiff
cargo set-version --bump patch -p tor-dirclient
cargo set-version --bump patch -p tor-dirmgr
cargo set-version --bump patch -p tor-error
cargo set-version --bump patch -p tor-hsservice
cargo set-version --bump patch -p tor-linkspec
cargo set-version --bump patch -p tor-llcrypto
cargo set-version --bump patch -p tor-netdir
cargo set-version --bump patch -p tor-netdoc
cargo set-version --bump patch -p tor-proto
cargo set-version --bump patch -p tor-rpcbase
cargo set-version --bump patch -p tor-socksproto
```

This crate has new features, but no new non-experimental Rust APIs.
So even though it is post-1.0, it gets a patchlevel bump.

```
cargo set-version --bump patch -p arti
```
</content>
</entry>
<entry>
<title>Bump minor versions on crates with breaking changes</title>
<updated>2023-06-30T12:38:16Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-06-30T12:38:16Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=65e81bf0ca876669a15943caf4cf388515366623'/>
<id>urn:sha1:65e81bf0ca876669a15943caf4cf388515366623</id>
<content type='text'>
Done with:
```
cargo set-version --bump minor -p tor-hsclient
cargo set-version --bump minor -p arti-rpcserver
cargo set-version --bump minor -p tor-hscrypto
cargo set-version --bump minor -p tor-cell
```
</content>
</entry>
<entry>
<title>Resolve XXXs from fixup-features.</title>
<updated>2023-06-29T21:14:00Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-06-29T21:14:00Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=a88fa71f25d888316f9b47b22a169525dbf7b2f2'/>
<id>urn:sha1:a88fa71f25d888316f9b47b22a169525dbf7b2f2</id>
<content type='text'>
Some of these seem spurious: it looks like fixup-features resolved
an issue and then complained about it too.  I'll investigate further.
</content>
</entry>
<entry>
<title>Run "fixup-features".</title>
<updated>2023-06-29T21:09:52Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-06-29T21:09:52Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=23c67d92e62f46629807c1c681267374b2dcd72e'/>
<id>urn:sha1:23c67d92e62f46629807c1c681267374b2dcd72e</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Mark all {hs,onion-serivce}-client features as non-experimental.</title>
<updated>2023-06-29T17:09:37Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-06-29T17:09:37Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=d164a9dac216536bf960c7cb6a1f43d25ca55dc6'/>
<id>urn:sha1:d164a9dac216536bf960c7cb6a1f43d25ca55dc6</id>
<content type='text'>
</content>
</entry>
</feed>
