<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-dirclient/Cargo.toml, branch arti-v1.1.1</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.1</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.1'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2023-02-01T15:36:29Z</updated>
<entry>
<title>Bump the patch version of every crate that had API additions</title>
<updated>2023-02-01T15:36:29Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-02-01T15:36:29Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=7c1b6a5a81e382be6210c7e2b0aae9695ad0bef4'/>
<id>urn:sha1:7c1b6a5a81e382be6210c7e2b0aae9695ad0bef4</id>
<content type='text'>
These crates had API or behavior changes that may affect downstream
crates. Fortunately, they're all version 0.x, and don't need minor
bumps for this.
</content>
</entry>
<entry>
<title>Bump the patch-level version of crates with _minor_ changes.</title>
<updated>2023-02-01T15:23:58Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-02-01T15:23:58Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=66f594a4b6fac81137886be90a7bda3687923d48'/>
<id>urn:sha1:66f594a4b6fac81137886be90a7bda3687923d48</id>
<content type='text'>
These changes influence behavior, but not effect compatibility.
(If I messed up, and any crate except for `arti` has non-breaking
API changes, that's still fine, since they are all version
0.x.)
</content>
</entry>
<entry>
<title>Complete our migration to base64ct.</title>
<updated>2023-01-20T13:06:30Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-01-19T19:50:07Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=889206cde4ef29d7d10bda546f8ad518eb09c290'/>
<id>urn:sha1:889206cde4ef29d7d10bda546f8ad518eb09c290</id>
<content type='text'>
This is in lieu of upgrading to the latest base64 crate, which has
a different API from the old one.  Since we have to migrate either
way, we might as well use base64ct everywhere.

I don't think that most of these cases _require_ constant-time
base64, but it won't hurt.
</content>
</entry>
<entry>
<title>Bump the minor version of every crate.</title>
<updated>2022-11-30T20:10:16Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-11-30T20:10:16Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=38bef96b99dbf17922dc601d4250abc0368b519f'/>
<id>urn:sha1:38bef96b99dbf17922dc601d4250abc0368b519f</id>
<content type='text'>
We made this job easy this time around: by incrementing our MSRV, we
have forced ourselves to do at least a minor bump everywhere.
</content>
</entry>
<entry>
<title>bump rust-version to 1.60 in every crate.</title>
<updated>2022-11-10T15:57:33Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-11-07T19:18:02Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=936920b26e43447a010e249a9b5a5b9f69ca0da1'/>
<id>urn:sha1:936920b26e43447a010e249a9b5a5b9f69ca0da1</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Require derive_more 0.99.3</title>
<updated>2022-11-03T11:37:23Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-11-01T10:59:37Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=48f48841e1aa99f0c76c2078812b003ec191540a'/>
<id>urn:sha1:48f48841e1aa99f0c76c2078812b003ec191540a</id>
<content type='text'>
0.99.[012] have a bug https://github.com/JelteF/derive_more/issues/114
which makes the Deref derive for bridgedesc::StateGuard not work
and therefore breaks minimal-versions CI.

It seems simpler to require the newer version everywhere.
</content>
</entry>
<entry>
<title>Bump minor version of tor-rtcompat and most of its dependents</title>
<updated>2022-10-03T14:01:46Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-10-03T14:01:46Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=102e3c221dfadd6578cc6001f0566897fa9acaf8'/>
<id>urn:sha1:102e3c221dfadd6578cc6001f0566897fa9acaf8</id>
<content type='text'>
(Since the APIs for the `Schedule::sleep*` functions changed, this
is a breaking change in tor-rtcompat.  Therefore, the Runtime trait
in tor-rtcompat is now a different trait.  Therefore, anything that
uses the Runtime trait in its APIs has also broken.)
</content>
</entry>
<entry>
<title>Bump crates that have had backward compatible API changes.</title>
<updated>2022-10-03T13:52:34Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-10-03T13:52:34Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=388e0cbab55490f41e1c8cd06631efed7f23a318'/>
<id>urn:sha1:388e0cbab55490f41e1c8cd06631efed7f23a318</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Bump crate versions in preparation for Arti 1.0.0 release.</title>
<updated>2022-09-01T12:59:49Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-09-01T12:52:51Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=96875ea20875e3a5cfc9f348365f19a158578190'/>
<id>urn:sha1:96875ea20875e3a5cfc9f348365f19a158578190</id>
<content type='text'>
Because we want to work more on ensuring that our semver stability
story is solid, we are _not_ bumping arti-client to 1.0.0 right now.

Here are the bumps we _are_ doing.  Crates with "minor" bumps have
had API breaks; crates with "patch" bumps have had new APIs added.

Note that `tor-congestion` is not bumped here: it's a new crate, and
hasn't been published before.

```
tor-basic-utils         minor
fs-mistrust             minor
tor-config              minor
tor-rtcompat            minor
tor-rtmock              minor
tor-llcrypto            patch
tor-bytes               patch
tor-linkspec            minor
tor-cell                minor
tor-proto               minor
tor-netdoc              patch
tor-netdir              minor
tor-persist             patch
tor-chanmgr             minor
tor-guardmgr            minor
tor-circmgr             minor
tor-dirmgr              minor
arti-client             minor
arti-hyper              minor
arti                    major
arti-bench              minor
arti-testing            minor
```
</content>
</entry>
<entry>
<title>Update patch-versions on crates without API changes.</title>
<updated>2022-09-01T12:45:02Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-09-01T12:45:02Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=b3f989d6894aba3a12ff6ca629aee508566baf76'/>
<id>urn:sha1:b3f989d6894aba3a12ff6ca629aee508566baf76</id>
<content type='text'>
Since our last round of releases, these crates have had either
trivial changes, or changes that did not affect their APIs.
Therefore we are bumping their versions, but not changing which
versions of them other crates depend on.
</content>
</entry>
</feed>
