<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-config, branch arti-v1.1.7</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.7</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.7'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2023-08-01T14:57:55Z</updated>
<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>tor-config: Remove unused ItemOrBool helper.</title>
<updated>2023-07-13T11:30:07Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2023-07-12T18:10:11Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=5b97b0b2ce31b3dbe1ab9cf0d33109457d1aea47'/>
<id>urn:sha1:5b97b0b2ce31b3dbe1ab9cf0d33109457d1aea47</id>
<content type='text'>
`ItemOrBool` is currently not used anywhere (it was previously used by
the keymgr config).
</content>
</entry>
<entry>
<title>Run maint/add_warning to actually apply new lint allows</title>
<updated>2023-07-10T12:49:51Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-07-10T11:19:32Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=473447a82e099fd52a674c28f5bc24b3e05208c0'/>
<id>urn:sha1:473447a82e099fd52a674c28f5bc24b3e05208c0</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Merge branch 'allow_missing_panics' into 'main'</title>
<updated>2023-07-07T12:53:46Z</updated>
<author>
<name>Ian Jackson</name>
<email>iwj@torproject.org</email>
</author>
<published>2023-07-07T12:53:46Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=80f397fb0b433a915e6d2dead6795f79e8dae2b0'/>
<id>urn:sha1:80f397fb0b433a915e6d2dead6795f79e8dae2b0</id>
<content type='text'>
add_warning: Tolerate clippy::missing_panics_doc

Closes #950

See merge request tpo/core/arti!1380</content>
</entry>
<entry>
<title>Run add_warning to remove `missing_panics_doc` deny.</title>
<updated>2023-07-06T18:32:23Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-07-06T18:32:23Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=03f9f9987a7ba42368d82363bef7f569e32ffe2c'/>
<id>urn:sha1:03f9f9987a7ba42368d82363bef7f569e32ffe2c</id>
<content type='text'>
Closes #950.
</content>
</entry>
<entry>
<title>tor-config: Use next_back() instead of rev().next()</title>
<updated>2023-07-03T12:34:54Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-07-03T12:34:54Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=1f49be1a774b1b778cc819d7b6d50d215297e72a'/>
<id>urn:sha1:1f49be1a774b1b778cc819d7b6d50d215297e72a</id>
<content type='text'>
This is a new warning^Wsuggestion from clippy nightly.
</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>tor-config: Remove semver.md</title>
<updated>2023-06-29T17:59:27Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2023-06-29T13:29:48Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=65f85b813cfcd3b016a06d18e21d8e15fc2c07ef'/>
<id>urn:sha1:65f85b813cfcd3b016a06d18e21d8e15fc2c07ef</id>
<content type='text'>
The APIs mentioned in semver.md are all `experimental` now so we don't
really need the file anymore.
</content>
</entry>
<entry>
<title>tor-config: Make ItemOrBool an experimental feature.</title>
<updated>2023-06-29T17:59:27Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2023-06-29T13:28:53Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=26eefdc564110c3d526850b1a38fedd49a84d0be'/>
<id>urn:sha1:26eefdc564110c3d526850b1a38fedd49a84d0be</id>
<content type='text'>
</content>
</entry>
<entry>
<title>config: Add ItemOrBool helper for deserializing a bool or a value.</title>
<updated>2023-06-29T17:59:27Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2023-06-23T18:58:17Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=450fa5c474e9e9181e316ff1f39706a6ce35983d'/>
<id>urn:sha1:450fa5c474e9e9181e316ff1f39706a6ce35983d</id>
<content type='text'>
This will enable us to support the new `keystore_dir` field, which can
be either a boolean indicating whether the keystore is disabled or
enabled and initialized with the default keystore dir, or a string which
points to a custom keystore directory (and implies the keystore is
enabled):
```
# use this path, fail if compiled out
# keystore = "/path/to/arti/keystore"
#
# use default path, fail if compiled out
# keystore = true
#
# disable
# keystore = false
```

Part of #891
</content>
</entry>
</feed>
