prepare actix-session release 0.6.1

actix · Mar 21, 2022 · bf41b4c · bf41b4c
1 parent 449abd6
commit bf41b4c
Show file tree

Hide file tree

Showing 5 changed files with 16 additions and 13 deletions.
diff --git a/actix-session/CHANGES.md b/actix-session/CHANGES.md
@@ -3,6 +3,10 @@
 ## Unreleased - 2021-xx-xx
 
 
+## 0.6.1 - 2022-03-21
+- No significant changes since `0.6.0`.
+
+
 ## 0.6.0 - 2022-03-15
 ### Added
 - `SessionMiddleware`, a middleware to provide support for saving/updating/deleting session state against a pluggable storage backend (see `SessionStore` trait). [#212]

diff --git a/actix-session/Cargo.toml b/actix-session/Cargo.toml
@@ -1,6 +1,6 @@
 [package]
 name = "actix-session"
-version = "0.6.0"
+version = "0.6.1"
 authors = [
   "Nikolay Kim <[email protected]>",
   "Luca Palmieri <[email protected]>",

diff --git a/actix-session/README.md b/actix-session/README.md
@@ -3,9 +3,9 @@
 > Session management for Actix Web applications.
 
 [![crates.io](https://img.shields.io/crates/v/actix-session?label=latest)](https://crates.io/crates/actix-session)
-[![Documentation](https://docs.rs/actix-session/badge.svg?version=0.6.0)](https://docs.rs/actix-session/0.6.0)
+[![Documentation](https://docs.rs/actix-session/badge.svg?version=0.6.1)](https://docs.rs/actix-session/0.6.1)
 ![Apache 2.0 or MIT licensed](https://img.shields.io/crates/l/actix-session)
-[![Dependency Status](https://deps.rs/crate/actix-session/0.6.0/status.svg)](https://deps.rs/crate/actix-session/0.6.0)
+[![Dependency Status](https://deps.rs/crate/actix-session/0.6.1/status.svg)](https://deps.rs/crate/actix-session/0.6.1)
 
 
 ## Documentation & Resources

diff --git a/actix-session/src/lib.rs b/actix-session/src/lib.rs
@@ -5,11 +5,11 @@
 //! influenced by the provided inputs (i.e. the request content) and whatever state the server
 //! queries while performing its processing.
 //!
-//! Stateless systems are easier to reason about, but they are not quite as powerful as we need them to
-//! be - e.g. how do you authenticate a user? The user would be forced to authenticate **for every
-//! single request**. That is, for example, how 'Basic' Authentication works. While it may work for
-//! a machine user (i.e. an API client), it is impractical for a person—you do not want a login
-//! prompt on every single page you navigate to!
+//! Stateless systems are easier to reason about, but they are not quite as powerful as we need them
+//! to be - e.g. how do you authenticate a user? The user would be forced to authenticate **for
+//! every single request**. That is, for example, how 'Basic' Authentication works. While it may
+//! work for a machine user (i.e. an API client), it is impractical for a person—you do not want a
+//! login prompt on every single page you navigate to!
 //!
 //! There is a solution - **sessions**. Using sessions the server can attach state to a set of
 //! requests coming from the same client. They are built on top of cookies - the server sets a

diff --git a/actix-session/src/middleware.rs b/actix-session/src/middleware.rs
@@ -190,15 +190,14 @@ pub enum SessionLength {
 pub enum CookieContentSecurity {
     /// The cookie content is encrypted when using `CookieContentSecurity::Private`.
     ///
-    /// Encryption guarantees confidentiality and integrity: the client cannot
-    /// tamper with the cookie content nor decode it, as long as the encryption key remains
-    /// confidential.
+    /// Encryption guarantees confidentiality and integrity: the client cannot tamper with the
+    /// cookie content nor decode it, as long as the encryption key remains confidential.
     Private,
 
     /// The cookie content is signed when using `CookieContentSecurity::Signed`.
     ///
-    /// Signing guarantees integrity, but it doesn't ensure confidentiality: the client
-    /// cannot tamper with the cookie content, but they can read it.
+    /// Signing guarantees integrity, but it doesn't ensure confidentiality: the client cannot
+    /// tamper with the cookie content, but they can read it.
     Signed,
 }