<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/arti-testing/Cargo.toml, branch ios-sqlite-hacks</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=ios-sqlite-hacks</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=ios-sqlite-hacks'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2023-09-05T16:25:24Z</updated>
<entry>
<title>Bump patchlevel (not dependents) on crates with trivial changes</title>
<updated>2023-09-05T16:25:24Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-09-05T16:25:24Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=a4badb9fdac5dd36ea173545f1ff417ccab1f49b'/>
<id>urn:sha1:a4badb9fdac5dd36ea173545f1ff417ccab1f49b</id>
<content type='text'>
This includes:

```
tor-basic-utils
caret
fs-mistrust
safelog
retry-error
tor-events
tor-units
tor-geoip
tor-rtcompat
tor-rpcbase
tor-protover
tor-socksproto
tor-checkable
tor-congestion
tor-persist
tor-circmgr
arti-rpcserver
arti-config
arti-hyper
arti-bench
arti-testing
tor-consdiff
```
</content>
</entry>
<entry>
<title>Update patchlevel for crates with nontrivial changes.</title>
<updated>2023-09-05T16:22:19Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-09-05T16:22:19Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=e251baa9a77415f3c605ff462a8ac0b3fa37660a'/>
<id>urn:sha1:e251baa9a77415f3c605ff462a8ac0b3fa37660a</id>
<content type='text'>
These are:

```
hashx
equix
tor-async-utils
tor-error
tor-config
tor-rtmock
tor-llcrypto
tor-bytes
tor-hscrypto
tor-hspow
tor-cert
tor-linkspec
tor-cell
tor-proto
tor-netdoc
tor-netdir
tor-chanmgr
tor-guardmgr
tor-dirmgr
tor-keymgr
tor-hsclient
tor-hsservice
arti-client

arti
```
</content>
</entry>
<entry>
<title>Merge branch 'bump_versions_117' into 'main'</title>
<updated>2023-08-01T15:40:26Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-08-01T15:40:26Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=3422169ff4158e56764e2f3c3d2fea31e8031fcd'/>
<id>urn:sha1:3422169ff4158e56764e2f3c3d2fea31e8031fcd</id>
<content type='text'>
Vesion bumps for 1.1.7.

See merge request tpo/core/arti!1458</content>
</entry>
<entry>
<title>Bump patchlevel versions of crates with trivial changes</title>
<updated>2023-08-01T15:03:56Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-08-01T15:01:13Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=5cc3fe162944aff8efb975ac966f0e91b6908281'/>
<id>urn:sha1:5cc3fe162944aff8efb975ac966f0e91b6908281</id>
<content type='text'>
These crates have had trivial changes only: typically,
changes to documentation or to clippy warnings.  There's no
good reason to update which version of them other crates depend on,
so we only bump _their_ patchlevels.

```
tor-async-utils
caret
safelog
tor-events
tor-units
tor-rtcompat
tor-rpcbase
tor-llcrypto
tor-protover
tor-bytes
tor-hscrypto
tor-socksproto
tor-cert
tor-cell
tor-consdiff
tor-congestion
arti-rpcserver
arti-testing
arti-bench
arti-config
arti-hyper
```
</content>
</entry>
<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>Run "fixup features" in preparation for a release.</title>
<updated>2023-08-01T12:32:20Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-08-01T12:32:20Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=9ce6f0a0eb32051ef36bed2c65f0794a5a04421d'/>
<id>urn:sha1:9ce6f0a0eb32051ef36bed2c65f0794a5a04421d</id>
<content type='text'>
</content>
</entry>
<entry>
<title>rng ranges: Use gen_range_infallible() for Duration::ZERO..=T</title>
<updated>2023-07-10T15:08:03Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-07-07T13:19:55Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=b151237a7f8651ed8694748832af05786a7eccfd'/>
<id>urn:sha1:b151237a7f8651ed8694748832af05786a7eccfd</id>
<content type='text'>
</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 versions on crates with nonfunctional changes</title>
<updated>2023-06-30T12:30:55Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-06-30T12:30:55Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=40768a9f6174609b1146c981e235b99e5953f364'/>
<id>urn:sha1:40768a9f6174609b1146c981e235b99e5953f364</id>
<content type='text'>
These crates have had nonfunctional changes only, mostly due to !1271,
or ac90cb7500f2f108, or documentation changes: crates that depend on
them do not require a version bump.

```
arti-bench
arti-config
arti-hyper
arti-testing
caret
fs-mistrust
retry-error
tor-async-utils
tor-basic-utils
tor-chanmgr
tor-checkable
tor-congestion
tor-consdiff
tor-events
tor-guardmgr
tor-persist
tor-protover
tor-ptmgr
tor-rtcompat
tor-rtmock
tor-units
```
</content>
</entry>
</feed>
