Upgrade to 0.9.1

.github/workflows/rust.yaml

@@ -38,7 +38,7 @@ jobs:
         name: Download duckdb
         with:
           repository: "duckdb/duckdb"
-          tag: "v0.9.0"
+          tag: "v0.9.1"
           fileName: ${{ matrix.duckdb }}
           out-file-path: .
 

Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "duckdb"
-version = "0.9.0"
+version = "0.9.1"
 authors = ["wangfenjin <[email protected]>"]
 edition = "2021"
 description = "Ergonomic wrapper for DuckDB"
@@ -79,7 +79,7 @@ polars-core = "0.33.2"
 
 [dependencies.libduckdb-sys]
 path = "libduckdb-sys"
-version = "0.9.0"
+version = "0.9.1"
 
 [package.metadata.docs.rs]
 features = []

README.md

@@ -93,8 +93,8 @@ You can adjust this behavior in a number of ways:
   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]
-  # Assume that version DuckDB version 0.9.0 is used.
-  duckdb = { version = "0.9.0", features = ["bundled"] }
+  # Assume that version DuckDB version 0.9.1 is used.
+  duckdb = { version = "0.9.1", features = ["bundled"] }
   ```
 * When linking against a DuckDB library already on the system (so *not* using any of the `bundled` features), you can set the `DUCKDB_LIB_DIR` environment variable to point to a directory containing the library. You can also set the `DUCKDB_INCLUDE_DIR` variable to point to the directory containing `duckdb.h`.
 * Installing the duckdb development packages will usually be all that is required, but

libduckdb-sys/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "libduckdb-sys"
-version = "0.9.0"
+version = "0.9.1"
 authors = ["wangfenjin <[email protected]>"]
 edition = "2021"
 build = "build.rs"