diff --git a/CHANGELOG.md b/CHANGELOG.md
index 2344546..f57d349 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -7,6 +7,7 @@ Only accretive/fixative changes will be made from now on.
 The following changes have been committed to the **master** branch since the 1.0.2 release:
 
 * Fix #48 by adding `next.jdbc.connection/->pool` and documenting how to use HikariCP and c3p0 in the Getting Started docs (as well as adding tests for both libraries).
+* Updated test dependencies (testing against more recent versions of several drivers).
 
 ## Stable Builds
 
diff --git a/README.md b/README.md
index ccf41af..e7c2950 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.2 release -- [see the CHANGELOG](CHANGELOG.md).
+This documentation is for **master** after the 1.0.2 release -- [see the CHANGELOG](CHANGELOG.md).
 
 * [Getting Started](/doc/getting-started.md)
 * [Migrating from `clojure.java.jdbc`](/doc/migration-from-clojure-java-jdbc.md)
@@ -26,7 +26,7 @@ Those were my three primary drivers. In addition, the `db-spec`-as-hash-map appr
 
 I also wanted `datafy`/`nav` support baked right in (it was added to `clojure.java.jdbc` back in December 2018 as an undocumented, experimental API in a separate namespace). It is the default behavior for `execute!` and `execute-one!`. The protocol-based function `next.jdbc.result-set/datafiable-row` can be used with `plan` if you need to add `datafy`/`nav` support to rows you are creating in your reduction.
 
-As `next.jdbc` moved from alpha to beta, the last breaking change was made (renaming `reducible!` to `plan`) and the API should now be considered stable. Only accretive and fixative changes will be made from now on.
+As `next.jdbc` moved from alpha to beta, the last breaking change was made (renaming `reducible!` to `plan`) and the API should be considered stable. Only accretive and fixative changes will be made from now on.
 
 After a month of alpha builds being available for testing, the first beta build was released on May 24th, 2019. A release candidate followed on June 4th and the "gold" (1.0.0) release was on June 12th. In addition to the small, core API in `next.jdbc`, there are "syntactic sugar" SQL functions (`insert!`, `query`, `update!`, and `delete!`) available in `next.jdbc.sql` that are similar to the main API in `clojure.java.jdbc`. See [Migrating from `clojure.java.jdbc`](/doc/migration-from-clojure-java-jdbc.md) for more detail about the differences.
 
diff --git a/deps.edn b/deps.edn
index ed6dff4..97df3db 100644
--- a/deps.edn
+++ b/deps.edn
@@ -3,20 +3,20 @@
         org.clojure/java.data {:mvn/version "0.1.1"}}
  :aliases
  {:test {:extra-paths ["test"]
-         :extra-deps {org.clojure/test.check {:mvn/version "0.9.0"}
+         :extra-deps {org.clojure/test.check {:mvn/version "0.10.0-RC1"}
                       ;; connection pooling
                       com.zaxxer/HikariCP {:mvn/version "3.3.1"}
                       com.mchange/c3p0 {:mvn/version "0.9.5.4"}
                       ;; JDBC drivers
-                      org.apache.derby/derby {:mvn/version "10.14.2.0"}
-                      org.hsqldb/hsqldb {:mvn/version "2.4.1"}
-                      com.h2database/h2 {:mvn/version "1.4.197"}
+                      org.apache.derby/derby {:mvn/version "10.14.2.0"} ; behind
+                      org.hsqldb/hsqldb {:mvn/version "2.5.0"}
+                      com.h2database/h2 {:mvn/version "1.4.199"}
                       net.sourceforge.jtds/jtds {:mvn/version "1.3.1"}
-                      mysql/mysql-connector-java {:mvn/version "5.1.41"}
-                      org.postgresql/postgresql {:mvn/version "42.2.2.jre7"}
-                      com.impossibl.pgjdbc-ng/pgjdbc-ng {:mvn/version "0.7.1"}
-                      org.xerial/sqlite-jdbc {:mvn/version "3.23.1"}
-                      com.microsoft.sqlserver/mssql-jdbc {:mvn/version "6.2.2.jre8"}}}
+                      mysql/mysql-connector-java {:mvn/version "5.1.41"} ; behind
+                      org.postgresql/postgresql {:mvn/version "42.2.6"}
+                      com.impossibl.pgjdbc-ng/pgjdbc-ng {:mvn/version "0.8.2"}
+                      org.xerial/sqlite-jdbc {:mvn/version "3.28.0"}
+                      com.microsoft.sqlserver/mssql-jdbc {:mvn/version "7.2.2.jre8"}}}
   :runner
   {:extra-deps {com.cognitect/test-runner
                 {:git/url "https://github.com/cognitect-labs/test-runner"
diff --git a/doc/getting-started.md b/doc/getting-started.md
index b41ecc2..b556118 100644
--- a/doc/getting-started.md
+++ b/doc/getting-started.md
@@ -147,8 +147,6 @@ If `with-transaction` is given a datasource, it will create and close the connec
 
 ## Connection Pooling
 
-(Coming soon in version 1.0.3!)
-
 `next.jdbc` makes it easy to use either HikariCP or c3p0 for connection pooling.
 
 First, you need to add the connection pooling library as a dependency, e.g.,