From b79bd4a6e13906d4b8a25a67c19c62c089cf7354 Mon Sep 17 00:00:00 2001
From: gwenn <gtreguier@gmail.com>
Date: Sat, 17 Feb 2024 09:42:27 +0100
Subject: [PATCH] Prepare release of version 0.31.0

---
 Cargo.toml                 | 4 ++--
 README.md                  | 8 ++++----
 rusqlite-macros/Cargo.toml | 2 +-
 3 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/Cargo.toml b/Cargo.toml
index dcdb256c1..562a7457e 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -1,7 +1,7 @@
 [package]
 name = "rusqlite"
 # Note: Update version in README.md when you change this.
-version = "0.30.0"
+version = "0.31.0"
 authors = ["The rusqlite developers"]
 edition = "2021"
 description = "Ergonomic wrapper for SQLite"
@@ -123,7 +123,7 @@ fallible-iterator = "0.3"
 fallible-streaming-iterator = "0.1"
 uuid = { version = "1.0", optional = true }
 smallvec = "1.6.1"
-rusqlite-macros = { path = "rusqlite-macros", version = "0.1.0", optional = true }
+rusqlite-macros = { path = "rusqlite-macros", version = "0.2.0", optional = true }
 
 [dev-dependencies]
 doc-comment = "0.3"
diff --git a/README.md b/README.md
index e7e21de26..ebb1eadd2 100644
--- a/README.md
+++ b/README.md
@@ -27,7 +27,7 @@ In your Cargo.toml:
 # That said, it's not ideal for all scenarios and in particular, generic
 # libraries built around `rusqlite` should probably not enable it, which
 # is why it is not a default feature -- it could become hard to disable.
-rusqlite = { version = "0.30.0", features = ["bundled"] }
+rusqlite = { version = "0.31.0", features = ["bundled"] }
 ```
 
 Simple example usage:
@@ -150,11 +150,11 @@ You can adjust this behavior in a number of ways:
 * If you use the `bundled`, `bundled-sqlcipher`, or `bundled-sqlcipher-vendored-openssl` features, `libsqlite3-sys` will use the
   [cc](https://crates.io/crates/cc) crate to compile SQLite or SQLCipher from source and
   link against that. This source is embedded in the `libsqlite3-sys` crate and
-  is currently SQLite 3.44.0 (as of `rusqlite` 0.30.0 / `libsqlite3-sys`
-  0.27.0).  This is probably the simplest solution to any build problems. You can enable this by adding the following in your `Cargo.toml` file:
+  is currently SQLite 3.45.1 (as of `rusqlite` 0.31.0 / `libsqlite3-sys`
+  0.28.0).  This is probably the simplest solution to any build problems. You can enable this by adding the following in your `Cargo.toml` file:
   ```toml
   [dependencies.rusqlite]
-  version = "0.30.0"
+  version = "0.31.0"
   features = ["bundled"]
   ```
 * When using any of the `bundled` features, the build script will honor `SQLITE_MAX_VARIABLE_NUMBER` and `SQLITE_MAX_EXPR_DEPTH` variables. It will also honor a `LIBSQLITE3_FLAGS` variable, which can have a format like `"-USQLITE_ALPHA -DSQLITE_BETA SQLITE_GAMMA ..."`. That would disable the `SQLITE_ALPHA` flag, and set the `SQLITE_BETA` and `SQLITE_GAMMA` flags. (The initial `-D` can be omitted, as on the last one.)
diff --git a/rusqlite-macros/Cargo.toml b/rusqlite-macros/Cargo.toml
index 67f2d20fb..5503800e0 100644
--- a/rusqlite-macros/Cargo.toml
+++ b/rusqlite-macros/Cargo.toml
@@ -1,6 +1,6 @@
 [package]
 name = "rusqlite-macros"
-version = "0.1.0"
+version = "0.2.0"
 authors = ["The rusqlite developers"]
 edition = "2021"
 description = "Private implementation detail of rusqlite crate"