<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/web-time-compat/Cargo.toml, branch arti-v2.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-v2.5.0</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v2.5.0'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2026-06-30T13:42:13Z</updated>
<entry>
<title>Version bumps for 2.5.0</title>
<updated>2026-06-30T13:42:13Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2026-06-30T13:42:13Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=245b03f5a48b4e58f8c84f072920160fc87be500'/>
<id>urn:sha1:245b03f5a48b4e58f8c84f072920160fc87be500</id>
<content type='text'>
Closes #2617.

We've lucked out this time, and it turns out that every one of our
published crates gets a minor bump.  So this was generated with:

```
for cr in $(./maint/list-crates); do
   cargo set-version -p $cr --bump minor
done
```
</content>
</entry>
<entry>
<title>Bump MSRV to 1.91</title>
<updated>2026-06-15T13:18:11Z</updated>
<author>
<name>Clara Engler</name>
<email>cve@cve.cx</email>
</author>
<published>2026-06-15T12:59:25Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=e93e0e2f9f42f526a8e1aa64e6ea659ef31dd800'/>
<id>urn:sha1:e93e0e2f9f42f526a8e1aa64e6ea659ef31dd800</id>
<content type='text'>
This commit bumps the MSRV to 1.91 which was released on 2025-10-30.

The Cargo.toml files were updated as follows:
```sh
git ls-files | \
    grep ".*Cargo\.toml$" | \
    xargs sed -i '' 's/^rust-version = "1\.89"$/rust-version = "1\.91"/g'
```

The following files were updated manually:
```
	modified:   .gitlab-ci.yml
	modified:   README.md
	modified:   flake.nix
	modified:   maint/docker-android/Dockerfile
```
</content>
</entry>
<entry>
<title>Add a new web-time-compat crate.</title>
<updated>2026-03-26T19:20:16Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2026-03-26T12:28:09Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=418d4b802c4fa269b2e47b7405c04fb72ff2f146'/>
<id>urn:sha1:418d4b802c4fa269b2e47b7405c04fb72ff2f146</id>
<content type='text'>
This crate provides a compatibility layer in front of web-time,
which will serve three purposes:

1. Saving us from having to build web_time when we don't need it.

   (This is mainly aesthetic.)

2. Allowing us to continue to use std::time::SystemTime to represent
   our wall-clock times and dates.

   This is fairly valuable, since we use a bunch of external crates
   that expect std::time::SystemTime inputs and don't want a
   web_time::SystemTime.

3. Add extension methods to web_time::Instant and std::time::Instant
   so that we can enforce the use of web_time::Instant by
   disallowing std::time::Instant::now().

   (We can't just use the same trick as in (2) to use
   std::time::Instant everywhere, since there is no way to convert a
   web_time::Instant to a std::time::Instant.)
</content>
</entry>
</feed>
