<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-netdir/Cargo.toml, branch arti-v0.5.0</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.5.0</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.5.0'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2022-06-24T16:00:22Z</updated>
<entry>
<title>Bump crate and dependency versions.</title>
<updated>2022-06-24T16:00:22Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-06-24T16:00:22Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=20435aea751331817709acde8d4b65b5fb8d8f12'/>
<id>urn:sha1:20435aea751331817709acde8d4b65b5fb8d8f12</id>
<content type='text'>
These were done with the following commands:

```
cargo set-version -p tor-basic-utils   --bump patch
cargo set-version -p fs-mistrust       --bump minor
cargo set-version -p tor-error         --bump patch
cargo set-version -p tor-config        --bump patch
cargo set-version -p tor-units         --bump patch
cargo set-version -p tor-rtcompat      --bump minor
cargo set-version -p tor-llcrypto      --bump patch
cargo set-version -p tor-bytes         --bump minor
cargo set-version -p tor-socksproto    --bump minor
cargo set-version -p tor-cert          --bump minor
cargo set-version -p tor-cell          --bump minor
cargo set-version -p tor-proto         --bump minor
cargo set-version -p tor-netdoc        --bump patch
cargo set-version -p tor-netdir        --bump minor
cargo set-version -p tor-persist       --bump patch
cargo set-version -p tor-chanmgr       --bump minor
cargo set-version -p tor-guardmgr      --bump minor
cargo set-version -p tor-circmgr       --bump patch
cargo set-version -p tor-dirclient     --bump patch
cargo set-version -p tor-dirmgr        --bump minor
cargo set-version -p arti-client       --bump patch
cargo set-version -p arti              --bump minor
cargo set-version -p arti-bench        --bump minor
cargo set-version -p arti-testing      --bump minor
```
</content>
</entry>
<entry>
<title>Upgrade to float_eq 1.0.0</title>
<updated>2022-06-16T12:39:03Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-06-16T12:39:03Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=519f7dfa881734a5ebb0cbe07868db834941cb46'/>
<id>urn:sha1:519f7dfa881734a5ebb0cbe07868db834941cb46</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Add "full" and "experimental" features to arti-client and below.</title>
<updated>2022-06-10T19:32:21Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-06-10T19:26:51Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=8a586a40fa4afbd5402737406b287dc488c6f66a'/>
<id>urn:sha1:8a586a40fa4afbd5402737406b287dc488c6f66a</id>
<content type='text'>
The "full" feature is a catch-all for all features, _except_:

   * Those that select a particular implementation (like
     tor-llcrypto/with-openssl) or build flag (like "static")
   * Those that are experimental or unstable (like "experimental-api")
   * Those that are testing-only.
</content>
</entry>
<entry>
<title>Rewrite tests in tor-netdir to use testing_rng()</title>
<updated>2022-06-02T19:48:41Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-06-02T19:39:45Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=1076f25031c16fdccbc80f3d16882b1267c2a800'/>
<id>urn:sha1:1076f25031c16fdccbc80f3d16882b1267c2a800</id>
<content type='text'>
The randomized tests in this crate take a lot of iterations to
converge, so they default to using a deterministic PRNG seed with
few iterations and higher tolerance, and they only randomize the
tests (with more iterations and tighter tolerances) when you
explicitly opt in to randomization.

(If you specify a seed explicitly, you're doing that to reproduce a
randomized case, so we use the same behavior.)
</content>
</entry>
<entry>
<title>Use testing_rng() in tests throughout our crates.</title>
<updated>2022-06-02T18:56:42Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-06-02T17:31:43Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=967ea67b7dfc158f29cf449eb09bac89acdee46b'/>
<id>urn:sha1:967ea67b7dfc158f29cf449eb09bac89acdee46b</id>
<content type='text'>
This only affects uses of thread_rng(), and affects them all more or
less indiscriminately.  One test does not work with
ARTI_TEST_PRNG=deterministic; the next commit will fix it.
</content>
</entry>
<entry>
<title>Lexically sort Cargo.toml dependencies</title>
<updated>2022-05-28T17:05:51Z</updated>
<author>
<name>Orhun Parmaksız</name>
<email>orhunparmaksiz@gmail.com</email>
</author>
<published>2022-05-28T16:41:39Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=bfd41ddb5fefe8808c33669c508dde4325808e35'/>
<id>urn:sha1:bfd41ddb5fefe8808c33669c508dde4325808e35</id>
<content type='text'>
Utilize cargo-sort: https://github.com/DevinR528/cargo-sort

Signed-off-by: Orhun Parmaksız &lt;orhunparmaksiz@gmail.com&gt;
</content>
</entry>
<entry>
<title>Regenerate version bump from previous commit.</title>
<updated>2022-05-27T14:18:52Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-05-27T14:18:52Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=4326aa1de9875ea399c3a608c0320bbe4b214a42'/>
<id>urn:sha1:4326aa1de9875ea399c3a608c0320bbe4b214a42</id>
<content type='text'>
This commit was made by reverting the previous commit, then
re-running the script I used to generate it.  In theory there should
be no semantic changes: only changes due to improved formatting from
cargo edit.
</content>
</entry>
<entry>
<title>Semantic version changes for Arti 0.4.0 release</title>
<updated>2022-05-27T13:01:20Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-05-27T13:01:20Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=b232365a75249d6f767127feb2a47286f9ece762'/>
<id>urn:sha1:b232365a75249d6f767127feb2a47286f9ece762</id>
<content type='text'>
I followed the following procedure to make these changes:

* I used maint/changed_crates to find out which crates had changed
  since 0.3.0.
* I used grep and maint/list_crates to sort those crates in
  topological (dependency) order.
* I looked through semver_status to find which crates were listed as
  having semver-relevant changes (new APIs and breaking changes).
* I scanned through the git logs of the crates with no
  semver-relevant changes listed to confirm that, indeed, they had
  no changes.  For those crates, I incremented their patch-level
  version _without_ changing the version that other crates depend on.
* I scanned through the git logs of the crates with no
  semver-relevant changes listed to confirm that, indeed, they had
  no obvious breaking changes.
* I treated all crates that depend on `arti` and/or `arti-client` as
  having breaking changes.
* I identified crates that depend on crates that have changed, even
  if they have not changed themselves, and identified them as having
  a non-breaking change.
* For all of the crates, I used `cargo set-version -p $CRATE --bump
  $STATUS` (where `STATUS` is `patch` or `minor`) to update the
  versions, and the depended-upon versions.
</content>
</entry>
<entry>
<title>Bump versions of trivially-changed crates.</title>
<updated>2022-05-27T12:52:44Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-05-27T12:52:44Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=45d21d2520cf083000e4384242f33796186de29b'/>
<id>urn:sha1:45d21d2520cf083000e4384242f33796186de29b</id>
<content type='text'>
These crates had only clippy fixes that do not affect their
behavior:
        tor-bytes
        tor-cell
        tor-events
        tor-linkspec
        tor-netdir
        tor-socksproto

This crate only had the cargo-husky dependency removed, which
does not affect compatibility:
        tor-llcrypto

Since these changes have no compatibility effects, it is not
necessary to bump the versions of these crates which other crates
depend on.
</content>
</entry>
<entry>
<title>Bump the version of every* crate to 0.3.0</title>
<updated>2022-05-06T14:03:15Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-05-06T14:03:15Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=7b93091f57f43ec8543a17052d60a2c8f7f2b0cc'/>
<id>urn:sha1:7b93091f57f43ec8543a17052d60a2c8f7f2b0cc</id>
<content type='text'>
* Except for safelog and fs-mistrust, which are new.
</content>
</entry>
</feed>
