mirrors/arti.git/crates/tor-rtcompat, branch arti-v1.4.3

release: Bump all unstable tor/arti crates to 0.30.0

2025-05-01T16:22:28Z

``` for crate in $(./maint/list_crates | rg '^(tor|arti-)'); do cargo set-version -p $crate 0.30.0 done ```

Merge branch 'fork' into 'main'

2025-04-14T14:06:59Z

Forbid fork, except very carefully before exec Closes #1897 See merge request tpo/core/arti!2925

Merge branch 'rtmock-unsend' into 'main'

2025-04-14T13:22:34Z

Relax bounds on BlockOn::reenter_block_on Closes #1933 See merge request tpo/core/arti!2934

tor-rtcompat: BlockOn: relax bounds on reenter_block_on

2025-04-09T16:52:03Z

The future no longer needs to be `Send + 'static`.

Allow StreamOps import to be unused

2025-04-09T16:25:51Z

This comes up on OSX; I hadn't seen it before, so I assume it is new with Rust 1.86.

tor-rtcompat: xref to fork policy from PreferredRuntime

2025-04-07T15:24:53Z

tor-rtcompat: Add div anchor for policy

2025-04-07T15:24:53Z

We're going to want to make many xrefs to this. This trick with the

has worked well for us in derive-deftly.

tor-rtcompat: Write policy on fork without exec

2025-04-07T15:24:53Z

Remove semver.md files post-release.

2025-04-01T11:27:04Z

tor-rtcompat: Avoid wildcard dependency requirements.

2025-04-01T10:13:21Z

This is preventing us from publishing `tor-rtcompat`: > error: failed to publish to registry at https://crates.io > > Caused by: > the remote server responded with an error (status 400 Bad Request): wildcard (`*`) dependency constraints are not allowed on crates.io. Crate with this problem: `hex` See https://doc.rust-lang.org/cargo/faq.html#can-libraries-use--as-a-version-for-their-dependencies for more information