From 30c5db1c95854628936705e0453a0031f4e60dc3 Mon Sep 17 00:00:00 2001 From: Sean Lawlor Date: Fri, 25 Oct 2024 13:27:30 -0400 Subject: [PATCH] Fix main docs prior to release --- README.md | 2 +- ractor/src/lib.rs | 2 +- ractor_cluster/README.md | 4 ++-- ractor_cluster/src/lib.rs | 1 - 4 files changed, 4 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 9266a178..34a6e45e 100644 --- a/README.md +++ b/README.md @@ -66,7 +66,7 @@ Install `ractor` by adding the following to your Cargo.toml dependencies. ```toml [dependencies] -ractor = "0.12" +ractor = "0.13" ``` The minimum supported Rust version (MSRV) of `ractor` is `1.64`. However to utilize the native `async fn` support in traits and not rely on the `async-trait` crate's desugaring functionliaty, you need to be on Rust version `>= 1.75`. The stabilization of `async fn` in traits [was recently added](https://blog.rust-lang.org/2023/12/21/async-fn-rpit-in-traits.html). diff --git a/ractor/src/lib.rs b/ractor/src/lib.rs index c2b84527..a814a318 100644 --- a/ractor/src/lib.rs +++ b/ractor/src/lib.rs @@ -12,7 +12,7 @@ //! //! ```toml //! [dependencies] -//! ractor = "0.12" +//! ractor = "0.13" //! ``` //! //! The minimum supported Rust version (MSRV) is 1.64. However if you disable the `async-trait` feature, then you need Rust >= 1.75 due to the native diff --git a/ractor_cluster/README.md b/ractor_cluster/README.md index 2893fd85..5d4cd9cb 100644 --- a/ractor_cluster/README.md +++ b/ractor_cluster/README.md @@ -27,8 +27,8 @@ Install `ractor_cluster` by adding the following to your Cargo.toml dependencies ```toml [dependencies] -ractor = { version = "0.12", features = ["cluster"] } -ractor_cluster = "0.12" +ractor = { version = "0.13", features = ["cluster"] } +ractor_cluster = "0.13" ``` ## Ractor in distribucted clusters diff --git a/ractor_cluster/src/lib.rs b/ractor_cluster/src/lib.rs index dab85cbd..c22eceb0 100644 --- a/ractor_cluster/src/lib.rs +++ b/ractor_cluster/src/lib.rs @@ -17,7 +17,6 @@ //! for binary serialization + deserialization. The "remote" actor will simply encode your message type and send it //! over the wire for you //! -//! //! (Future) When nodes connect, they identify all of the nodes the remote node is also connected to and additionally connect //! to them as well. //!