CHANGELOG.md

@@ -4,7 +4,6 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).
 
 Procedure when bumping the version number:
-
 1. Update dependencies in a separate commit
 2. Set version number in `Cargo.toml`
 3. Add new section in this changelog
@@ -14,44 +13,22 @@ Procedure when bumping the version number:
 
 ## Unreleased
 
-### Changed
-
-- **(breaking)** Bumped `rusqlite` dependency from `0.32` to `0.33`
-
-## v0.5.0 - 2024-09-04
-
-### Changed
-
-- **(breaking)** Bumped `rusqlite` dependency from `0.31` to `0.32`
-
-## v0.4.0 - 2024-02-23
-
-### Changed
-
-- **(breaking)** Bumped `rusqlite` dependency from `0.30` to `0.31`
-
-## v0.3.0 - 2023-12-26
-
-### Changed
-
-- **(breaking)** Bumped `rusqlite` dependency from `0.29` to `0.30`
-
 ## v0.2.0 - 2023-05-14
 
 ### Added
-
 - `serde` feature
 - `serde::from_row_via_index`
 - `serde::from_row_via_name`
 
 ### Changed
-
 - **(breaking)**
   Error handling of `Action`s is now more complex but more powerful. In
   particular, `Action`s can now return almost arbitrary errors without nesting
   `Result`s like before.
-- **(breaking)** Renamed `Action::Result` to `Action::Output`
+- **(breaking)**
-- **(breaking)** Bumped `rusqlite` dependency from `0.28` to `0.29`
+  Renamed `Action::Result` to `Action::Output`
+- **(breaking)**
+  Bumped `rusqlite` dependency from `0.28` to `0.29`
 
 ## v0.1.0 - 2023-02-12
 

Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "vault"
-version = "0.5.0"
+version = "0.2.0"
 edition = "2021"
 
 [features]
@@ -8,6 +8,6 @@ serde = ["dep:serde"]
 tokio = ["dep:tokio"]
 
 [dependencies]
-rusqlite = "0.33.0"
+rusqlite = "0.29.0"
-serde = { version = "1.0.209", optional = true }
+serde = { version = "1.0.163", optional = true }
-tokio = { version = "1.40.0", features = ["sync"], optional = true }
+tokio = { version = "1.28.1", features = ["sync"], optional = true }

src/simple.rs

@@ -34,13 +34,13 @@ impl SimpleVault {
     ///
     /// The `prepare` parameter allows access to the database after all
     /// migrations have occurred. This parameter could be replaced by executing
-    /// an [`Action`] performing the same operations.
     ///
     /// It is recommended to set a few pragmas before calling this function, for
     /// example:
     /// - `journal_mode` to `"wal"`
     /// - `foreign_keys` to `true`
     /// - `trusted_schema` to `false`
+    /// an [`Action`] performing the same operations.
     pub fn new_and_prepare(
         mut conn: Connection,
         migrations: &[Migration],