<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/arti-bench/Cargo.toml, branch tor-llcrypto-v0.4.4</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=tor-llcrypto-v0.4.4</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=tor-llcrypto-v0.4.4'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2023-03-31T12:28:06Z</updated>
<entry>
<title>Bump crate versions that have breaking changes</title>
<updated>2023-03-31T12:28:06Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-03-31T12:28:06Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=e208fb15adb800ae41e472db464f984e9f4a4f5c'/>
<id>urn:sha1:e208fb15adb800ae41e472db464f984e9f4a4f5c</id>
<content type='text'>
These crates have had breaking changes.  They are pre-1.0, so they get
a minor bump.

```
tor-basic-utils
tor-config
```
</content>
</entry>
<entry>
<title>Bump patchlevel on crates with non-breaking changes</title>
<updated>2023-03-31T12:24:39Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-03-31T12:24:39Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=a81ab391ae9cc3b48cf08cf1b911f1b4cfa8be76'/>
<id>urn:sha1:a81ab391ae9cc3b48cf08cf1b911f1b4cfa8be76</id>
<content type='text'>
For these crates, the changes are nontrivial, so we
_do_ bump the versions on which their dependent crates depend.

Fortunately, since they are all pre-1.0, we don't need to
distinguish semver-additions from other changes.  (Except for arti,
which _is_ post-1.0, but gets a patchlevel bump anyway.)

These are unstable crates with breaking changes:

```
tor-hscrypto
tor-hsclient
```

These have new or extended APIs:

```
safelog
tor-bytes
tor-cell
tor-linkspec
tor-llcrypto
tor-proto
tor-cert
arti-client
```

These have new unstable APIs or features:
```
tor-netdoc
tor-circmgr (also broke some unstable APIs)
arti (is post-1.0)
```

These have bugfixes only:
```
caret
tor-dirmgr
```
</content>
</entry>
<entry>
<title>Bump patchlevel on crates with semver-irrelevant changes.</title>
<updated>2023-03-31T12:20:58Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-03-31T12:20:58Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=622c79aaa60e433712a7dc4d7b8900659fc78071'/>
<id>urn:sha1:622c79aaa60e433712a7dc4d7b8900659fc78071</id>
<content type='text'>
Their dependents are _not_ updated to a more recent version.

These bumped the version of a dependency that they don't expose
```
tor-rtcompat
fs-mistrust
```

This one had internal refactoring:
```
tor-netdir
```

These had trivial changes only:
```
tor-checkable
tor-ptmgr
tor-guardmgr
arti-hyper
arti-bench
arti-testing
```
</content>
</entry>
<entry>
<title>Follow-on patchlevel bumps for crates with changed dependencies</title>
<updated>2023-02-28T12:18:37Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-02-28T12:18:37Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=2c9f8e35479fb2b59bb51de3efb424b0b1df4a56'/>
<id>urn:sha1:2c9f8e35479fb2b59bb51de3efb424b0b1df4a56</id>
<content type='text'>
These crates didn't have any changes until now, when I bumped
the versions of some other crates they depend on:

tor-consdiff
arti-hyper
arti-bench
arti-testing
</content>
</entry>
<entry>
<title>Patchlevel bumps for remaining changed crates.</title>
<updated>2023-02-28T12:13:27Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-02-28T12:13:27Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=f41449d0bd9a2db5f72dd9941fb897e5cd9b922d'/>
<id>urn:sha1:f41449d0bd9a2db5f72dd9941fb897e5cd9b922d</id>
<content type='text'>
These crates have had small code changes, but no API additions:

tor-config
tor-socksproto
tor-cert
tor-chanmgr
tor-ptmgr
tor-guardmgr
tor-circmgr
tor-dirclient
tor-dirmgr
arti
tor-hsservice
tor-congestion

These crates have had API extensions:

fs-mistrust
tor-llcrypto
tor-bytes
tor-checkable
tor-linkspec
tor-netdoc
tor-persist
arti-client
</content>
</entry>
<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>
</feed>
