<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-hscrypto/Cargo.toml, branch arti-v1.3.2</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.3.2</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.3.2'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2025-01-07T16:01:41Z</updated>
<entry>
<title>Bump versions of internal arti crates for Arti 1.3.2</title>
<updated>2025-01-07T16:01:41Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-01-07T14:46:55Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=8f4297f5e2712213910b50ced205c7b5aa0619b5'/>
<id>urn:sha1:8f4297f5e2712213910b50ced205c7b5aa0619b5</id>
<content type='text'>
The affected crates follow our regular versioning.
They all get bumped to 0.26.0.

Done with

```
for crate in $(./maint/list_crates |grep  '^arti-\|tor-' ); do
    cargo set-version --bump minor -p $crate;
done
```
</content>
</entry>
<entry>
<title>Merge branch 'upgrades' into 'main'</title>
<updated>2025-01-06T15:56:07Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-01-06T15:56:07Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=684215d2fbda7d13792e0d8d09a12ac4b9db6636'/>
<id>urn:sha1:684215d2fbda7d13792e0d8d09a12ac4b9db6636</id>
<content type='text'>
Simple dependency upgrades for upcoming release

See merge request tpo/core/arti!2685</content>
</entry>
<entry>
<title>Upgrade to itertools 0.14.0</title>
<updated>2025-01-06T13:10:39Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-01-06T13:10:39Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=a7f3cacea1eb5657ee1fee6d49594b1a58841519'/>
<id>urn:sha1:a7f3cacea1eb5657ee1fee6d49594b1a58841519</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Run "fixup-features" in preparation for release.</title>
<updated>2025-01-06T13:05:00Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-01-06T13:02:37Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=8810732cf7cf79c4746e8eac006d326f21d26c5f'/>
<id>urn:sha1:8810732cf7cf79c4746e8eac006d326f21d26c5f</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-hscrypto: Move encodable key trait impls from tor-key-forge.</title>
<updated>2024-12-11T16:13:10Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2024-12-11T16:11:54Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=cf6998c7e8fa42d29847759d96af3c5fe02ab5f0'/>
<id>urn:sha1:cf6998c7e8fa42d29847759d96af3c5fe02ab5f0</id>
<content type='text'>
This enables us to get rid of the tor-key-forge -&gt; tor-hscrypto
dependency, partially addressing the TODO from `tor_key_forge::traits`.

This commit is mostly code motion. Best reviewed with `--color-moved`.

See also #1778
</content>
</entry>
<entry>
<title>Bump all the unstable tor- and arti- crates to 0.25.0.</title>
<updated>2024-12-02T15:41:21Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2024-12-02T15:39:29Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=e29e7a9aab4312af6a35818cb01676376d888e49'/>
<id>urn:sha1:e29e7a9aab4312af6a35818cb01676376d888e49</id>
<content type='text'>
Done using:

```
for crate in $(./maint/list_crates  | rg '^(tor|arti-)'); do
    cargo set-version -p $crate 0.25.0
done
```
</content>
</entry>
<entry>
<title>Bump the versions of the non-{arti-,tor-} crates.</title>
<updated>2024-12-02T15:41:21Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2024-12-02T15:32:52Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=158ff2d2c0ef59ce6cdf5e8d6fe499b50e762002'/>
<id>urn:sha1:158ff2d2c0ef59ce6cdf5e8d6fe499b50e762002</id>
<content type='text'>
The non-{arti-,tor-} crates are:
```
./maint/list_crates  | rg -v '^(tor|arti)'
oneshot-fused-workaround
slotmap-careful
test-temp-dir
fslock-guard
hashx
equix
caret
fs-mistrust
safelog
retry-error
```

We split them in the following categories:
  * crates with no changes (no version bumps):
    ```
    maint/changed_crates -v "arti-v$LAST_VERSION" 2&gt;&amp;1 &gt;/dev/null | grep -i "no change" | grep -v '\(tor\|arti\)-'

         oneshot-fused-workaround: No change.
         test-temp-dir: No change.
         caret: No change.
    ```

  * crates that only have non-functional changes (bump the patch version):
     - slotmap-careful
     - fslock-guard
     - hashx
     - equix
     - fs-mistrust
     - safelog
     - retry-error

  * crates where APIs were broken (bump minor):
     None

The bumps from this commit were created using this script:

```
PATCH="
slotmap-careful
fslock-guard
hashx
equix
fs-mistrust
safelog
retry-error
"

for crate in $PATCH; do
    cargo set-version --bump patch -p $crate;
done
```
</content>
</entry>
<entry>
<title>PoW: Consolidate feature flags into a single flag.</title>
<updated>2024-11-25T20:49:46Z</updated>
<author>
<name>Wesley Aptekar-Cassels</name>
<email>me@wesleyac.com</email>
</author>
<published>2024-11-25T20:45:58Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=7846ed242bf39d9b366f47393de28056d70abec0'/>
<id>urn:sha1:7846ed242bf39d9b366f47393de28056d70abec0</id>
<content type='text'>
This replaces the hs-pow, hs-pow-full, hs-pow-v1, pow-v1, and pow-full
features with a single hs-pow-full feature.

It's possible that in the future we will want to split different schemes
into different features, but we can do that when it comes up.

For now, having this as a single flag makes it clearer what's going on,
since the previous thing was not actually expressive enough to capture
some things we care about (like "at least one pow scheme is enabled"
that works in a future-compatible way).

This change is not semver breaking since it's a experimental feature.

Related: #1751
</content>
</entry>
<entry>
<title>cargo: Update `thiserror` to `2`</title>
<updated>2024-11-12T17:00:30Z</updated>
<author>
<name>Clara Engler</name>
<email>cve@cve.cx</email>
</author>
<published>2024-11-12T10:04:54Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=2f00918ad55881fb8fb37ad51eb644c8aaa16a23'/>
<id>urn:sha1:2f00918ad55881fb8fb37ad51eb644c8aaa16a23</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Merge branch 'versions' into 'main'</title>
<updated>2024-10-30T18:21:11Z</updated>
<author>
<name>Ian Jackson</name>
<email>iwj@torproject.org</email>
</author>
<published>2024-10-30T18:21:11Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=6f24257bdf1a075cf09b41787d834bcc1a37f3a3'/>
<id>urn:sha1:6f24257bdf1a075cf09b41787d834bcc1a37f3a3</id>
<content type='text'>
Version bumps for release of 1.3.0

See merge request tpo/core/arti!2599</content>
</entry>
</feed>
