<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-rtmock/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:30:14Z</updated>
<entry>
<title>Patchlevel bumps for crates whose dependencies just changed.</title>
<updated>2023-03-31T12:30:14Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-03-31T12:30:14Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=9ef115a7fb21fe7267d1d91ba7babac8e1b7542e'/>
<id>urn:sha1:9ef115a7fb21fe7267d1d91ba7babac8e1b7542e</id>
<content type='text'>
These crates had no changes until just a moment ago. But since
we updated the versions on some of their dependents, they have now
changed themselves.  Thus they get patchlevel bumps.

```
tor-rtmock
tor-protover
tor-socksproto
tor-consdiff
tor-chanmgr
tor-dirclient
tor-hsservice
```
</content>
</entry>
<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 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>Use parse_rfc3339() in the tor-rtmock crate</title>
<updated>2022-12-16T21:07:49Z</updated>
<author>
<name>Neel Chauhan</name>
<email>neel@neelc.org</email>
</author>
<published>2022-12-16T21:07:49Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=11958c924153f96d4412448329c35dcb7f7f8c22'/>
<id>urn:sha1:11958c924153f96d4412448329c35dcb7f7f8c22</id>
<content type='text'>
</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>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>
<entry>
<title>enable doc_auto_cfg feature on every crate when documenting for docs.rs</title>
<updated>2022-08-24T16:22:41Z</updated>
<author>
<name>trinity-1686a</name>
<email>trinity@deuxfleurs.fr</email>
</author>
<published>2022-08-17T19:13:13Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=7f939fa4804b3c934343141b79e8e2ded5fe0b0d'/>
<id>urn:sha1:7f939fa4804b3c934343141b79e8e2ded5fe0b0d</id>
<content type='text'>
</content>
</entry>
</feed>
