From bde9c2d0743c2ea20d3e7fd4db4e54d9e5fb4fe6 Mon Sep 17 00:00:00 2001
From: Sean Corfield <sean@corfield.org>
Date: Fri, 11 Oct 2019 11:35:46 -0700
Subject: [PATCH] Prep for 1.0.9 release

---
 CHANGELOG.md           | 13 ++++++++-----
 README.md              |  2 +-
 doc/getting-started.md |  6 +++---
 pom.xml                |  2 +-
 4 files changed, 13 insertions(+), 10 deletions(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index 19a7a5a..8a438f2 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -4,15 +4,18 @@ 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.8 release:
+The following changes have been committed to the **master** branch since the 1.0.9 release:
 
-* Address #69 by trying to clarify when to use `execute-one!` vs `execute!` vs `plan`.
-* Address #68 by clarifying that builder functions do not affect the "fake result set" containing `:next.jdbc/update-count`.
-* Fix #67 by adding `:jdbcUrl` version spec.
-* Add `next.jdbc.optional/as-maps-adapter` to provide a way to override the default result set reading behavior of using `.getObject` when omitting SQL `NULL` values from result set maps.
+* None.
 
 ## Stable Builds
 
+* 2019-10-11 -- 1.0.9
+  * Address #69 by trying to clarify when to use `execute-one!` vs `execute!` vs `plan`.
+  * Address #68 by clarifying that builder functions do not affect the "fake result set" containing `:next.jdbc/update-count`.
+  * Fix #67 by adding `:jdbcUrl` version spec.
+  * Add `next.jdbc.optional/as-maps-adapter` to provide a way to override the default result set reading behavior of using `.getObject` when omitting SQL `NULL` values from result set maps.
+
 * 2019-09-27 -- 1.0.8
   * Fix #66 by adding support for a db-spec hash map format containing a `:jdbcUrl` key (consistent with `->pool`) so that you can create a datasource from a JDBC URL string and additional options.
   * Address #65 by adding a HugSQL "quick start" to the **Friendly SQL Functions** section of the docs.
diff --git a/README.md b/README.md
index d8dcf8d..2d7d28f 100644
--- a/README.md
+++ b/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 the 1.0.8 release -- [see the CHANGELOG](CHANGELOG.md).
+This documentation is for the 1.0.9 release -- [see the CHANGELOG](CHANGELOG.md).
 
 * [Getting Started](/doc/getting-started.md)
 * [Migrating from `clojure.java.jdbc`](/doc/migration-from-clojure-java-jdbc.md)
diff --git a/doc/getting-started.md b/doc/getting-started.md
index 36d74b8..86ea193 100644
--- a/doc/getting-started.md
+++ b/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.8"}}
+{seancorfield/next.jdbc {:mvn/version "1.0.9"}}
 ```
 for `deps.edn` or:
 
 ```clojure
-[seancorfield/next.jdbc "1.0.8"]
+[seancorfield/next.jdbc "1.0.9"]
 ```
 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.8"}
+        seancorfield/next.jdbc {:mvn/version "1.0.9"}
         com.h2database/h2 {:mvn/version "1.4.199"}}}
 ```
 
diff --git a/pom.xml b/pom.xml
index c8b86a8..5df349e 100644
--- a/pom.xml
+++ b/pom.xml
@@ -3,7 +3,7 @@
   <modelVersion>4.0.0</modelVersion>
   <groupId>seancorfield</groupId>
   <artifactId>next.jdbc</artifactId>
-  <version>1.0.8</version>
+  <version>1.0.9</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>