Prep for 1.0.1 release

CHANGELOG.md

@@ -4,16 +4,19 @@ Only accretive/fixative changes will be made from now on.
 
 ## Unreleased Changes
 
-The following changes have been committed to the **master** branch since the 1.0.0 release:
+The following changes have been committed to the **master** branch since the 1.0.1 release:
 
-* Fix #37 by adjusting the spec for `with-transaction` to "require less" of the `:binding` vector.
+* None.
-* Fix #36 by adding type hint in `with-transaction` macro.
-* Fix #35 by explaining the database-specific options needed to ensure `insert-multi!` performs a single, batched operation.
-* Fix #34 by explaining save points (in the Transactions documentation).
-* Fix #33 by updating the spec for the example `key-map` in `find-by-keys`, `update!`, and `delete!` to reflect that you cannot pass an empty map to these functions (and added tests to ensure the calls fail with spec errors).
 
 ## Stable Builds
 
+* 2019-07-03 -- 1.0.1
+  * Fix #37 by adjusting the spec for `with-transaction` to "require less" of the `:binding` vector.
+  * Fix #36 by adding type hint in `with-transaction` macro.
+  * Fix #35 by explaining the database-specific options needed to ensure `insert-multi!` performs a single, batched operation.
+  * Fix #34 by explaining save points (in the Transactions documentation).
+  * Fix #33 by updating the spec for the example `key-map` in `find-by-keys`, `update!`, and `delete!` to reflect that you cannot pass an empty map to these functions (and added tests to ensure the calls fail with spec errors).
+
 * 2019-06-12 -- 1.0.0 "gold"
   * Address #31 by making `reify`'d objects produce a more informative string representation if they are printed (e.g., misusing `plan` by not reducing it or not mapping an operation over the rows).
   * Fix #26 by exposing `next.jdbc.result-set/datafiable-result-set` so that various `java.sql.DatabaseMetaData` methods that return result metadata information in `ResultSet`s can be easily turned into a fully realized result set.

README.md

@@ -8,7 +8,7 @@ The latest versions on Clojars and on cljdoc:
 
 [![Clojars Project](https://clojars.org/seancorfield/next.jdbc/latest-version.svg)](https://clojars.org/seancorfield/next.jdbc) [![cljdoc badge](https://cljdoc.org/badge/seancorfield/next.jdbc)](https://cljdoc.org/d/seancorfield/next.jdbc/CURRENT)
 
-This documentation is for **master**, beyond the 1.0.0 release -- [see the CHANGELOG](CHANGELOG.md).
+This documentation is for the 1.0.1 release -- [see the CHANGELOG](CHANGELOG.md).
 
 * [Getting Started](/doc/getting-started.md)
 * [Migrating from `clojure.java.jdbc`](/doc/migration-from-clojure-java-jdbc.md)

doc/getting-started.md

@@ -9,12 +9,12 @@ It is designed to work with Clojure 1.10 or later, supports `datafy`/`nav`, and
 You can add `next.jdbc` to your project with either:
 
 ```clojure
-{seancorfield/next.jdbc {:mvn/version "1.0.0"}}
+{seancorfield/next.jdbc {:mvn/version "1.0.1"}}
 ```
 for `deps.edn` or:
 
 ```clojure
-[seancorfield/next.jdbc "1.0.0"]
+[seancorfield/next.jdbc "1.0.1"]
 ```
 for `project.clj` or `build.boot`.
 
@@ -29,7 +29,7 @@ For the examples in this documentation, we will use a local H2 database on disk,
 ```clojure
 ;; deps.edn
 {:deps {org.clojure/clojure {:mvn/version "1.10.1"}
-        seancorfield/next.jdbc {:mvn/version "1.0.0"}
+        seancorfield/next.jdbc {:mvn/version "1.0.1"}
         com.h2database/h2 {:mvn/version "1.4.197"}}}
 ```
 

pom.xml

@@ -3,7 +3,7 @@
   <modelVersion>4.0.0</modelVersion>
   <groupId>seancorfield</groupId>
   <artifactId>next.jdbc</artifactId>
-  <version>1.0.0</version>
+  <version>1.0.1</version>
   <name>next.jdbc</name>
 
   <description>The next generation of clojure.java.jdbc: a new low-level Clojure wrapper for JDBC-based access to databases.</description>