<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-persist, 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>clippy: deny `mod_module_files`</title>
<updated>2025-01-06T23:09:41Z</updated>
<author>
<name>Steven Engler</name>
<email>opara@torproject.org</email>
</author>
<published>2025-01-06T23:02:49Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=252a3a803b2db65792db5bd51dee8950d8557e0d'/>
<id>urn:sha1:252a3a803b2db65792db5bd51dee8950d8557e0d</id>
<content type='text'>
Denies 'mod.rs' files for consistency.

https://rust-lang.github.io/rust-clippy/master/index.html#mod_module_files
</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>add_warnings, *: Allow clippy::needless_lifetimes</title>
<updated>2024-12-03T14:27:26Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-12-03T14:15:50Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=64cc3f2ed3eea0b7c5cc89ae07cbdadfdc1646fb'/>
<id>urn:sha1:64cc3f2ed3eea0b7c5cc89ae07cbdadfdc1646fb</id>
<content type='text'>
In 1.83, this warning triggers on many of our crates.
We're thinking of fixing them all, but for now,
we're going to disable the warning.

This is part of #1765.
</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>tor-persist: Bump sanitize-filename to 0.6.0.</title>
<updated>2024-11-28T14:44:07Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2024-11-28T14:38:05Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=3cde446dbbc3fd5577fffb61e4c071b4b6083a13'/>
<id>urn:sha1:3cde446dbbc3fd5577fffb61e4c071b4b6083a13</id>
<content type='text'>
I couldn't find a changelog, but judging from the commit history, it
looks like they've bumped their regex dep, updated their MSRV to 1.70,
replaced lazy_static with OnceLock internally.
</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>tor-relay-crypto: Add a denotator to RelaySigningKeypairSpecifier.</title>
<updated>2024-10-31T14:34:51Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2024-10-23T11:00:33Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=8357c7c6fe01fd4c59e353a39ff59642bff0c19a'/>
<id>urn:sha1:8357c7c6fe01fd4c59e353a39ff59642bff0c19a</id>
<content type='text'>
This will enable us to store more than one `K_relaysign_ed` in the
keystore.

Closes #1692
</content>
</entry>
<entry>
<title>tor-persist: Add a slug timestamp type.</title>
<updated>2024-10-31T14:34:01Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2024-10-23T11:43:21Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=38d1e334007143bba5ec4b483f9e04b1f3ea23a1'/>
<id>urn:sha1:38d1e334007143bba5ec4b483f9e04b1f3ea23a1</id>
<content type='text'>
The new `Iso8601TimeSlug` is useful for encoding a timestamp as a `Slug`
(i.e. in a filename).

This is needed, for example, for #1692, to encode a timestamp as key
denotator.
</content>
</entry>
</feed>
