<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/arti-bench/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>Bump the patch version of each crate with _trivial_ changes.</title>
<updated>2023-02-01T15:10:36Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-02-01T15:10:36Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=592d6bf8a3980cf383306e894215add2a5e9e6cd'/>
<id>urn:sha1:592d6bf8a3980cf383306e894215add2a5e9e6cd</id>
<content type='text'>
These crates have not had changes to their behavior; as such it is
not necessary to bump their dependencies to require the new versions.
</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>Upgrade to clap 3: replace deprecated functions</title>
<updated>2022-11-04T18:28:40Z</updated>
<author>
<name>Gabriel de Perthuis</name>
<email>g2p.code@gmail.com</email>
</author>
<published>2022-11-04T12:08:09Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=21a3808684684ef659ba68c6534ae722d7b6b04c'/>
<id>urn:sha1:21a3808684684ef659ba68c6534ae722d7b6b04c</id>
<content type='text'>
Also replace Arg::takes_value with Arg::action to configure flags
that don't take parameters vs options that do.

This makes it easy to upgrade to clap 4.

Tested deprecations with:

    cargo check --workspace --all-features --features clap/deprecated
</content>
</entry>
<entry>
<title>Upgrade to clap 3 with minimal changes</title>
<updated>2022-11-04T18:28:38Z</updated>
<author>
<name>Gabriel de Perthuis</name>
<email>g2p.code@gmail.com</email>
</author>
<published>2022-11-04T09:52:02Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=bc08ea48f7f29c35e73d3dbf0aca23d85877a12f'/>
<id>urn:sha1:bc08ea48f7f29c35e73d3dbf0aca23d85877a12f</id>
<content type='text'>
This removes the last cargo audit override (for the unmaintained
ansi_term).

Don't mark options as required when they have default values:
see &lt;https://github.com/clap-rs/clap/pull/3793&gt;.
</content>
</entry>
<entry>
<title>Bump patchlevels of binary crates.</title>
<updated>2022-10-03T14:07:19Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-10-03T14:07:19Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=c1e70b7af4c32c2327e4c2c31bb31e60b677de9f'/>
<id>urn:sha1:c1e70b7af4c32c2327e4c2c31bb31e60b677de9f</id>
<content type='text'>
Since these don't expose any Runtime-based APIs, they don't have
a breaking change.
</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 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>
</feed>
