From ce0c99a3bfa63f076726aedc2d12b732fe526f49 Mon Sep 17 00:00:00 2001
From: parsonsmatt <parsonsmatt@gmail.com>
Date: Mon, 4 Mar 2019 17:56:30 -0700
Subject: [PATCH] 2.6.1

---
 changelog.md    | 7 +++++++
 esqueleto.cabal | 4 ++--
 package.yaml    | 2 +-
 3 files changed, 10 insertions(+), 3 deletions(-)

diff --git a/changelog.md b/changelog.md
index d87db22..b1d972d 100644
--- a/changelog.md
+++ b/changelog.md
@@ -1,6 +1,13 @@
 Unreleased
 ========
 
+2.6.1
+=======
+
+- @ChrisCoffey
+  - [#114](https://github.com/bitemyapp/esqueleto/pull/114): Fix Haddock by
+    working around an upstream bug.
+
 2.6.0
 ========
 - @bitemyapp
diff --git a/esqueleto.cabal b/esqueleto.cabal
index b92d7f9..a6b7d88 100644
--- a/esqueleto.cabal
+++ b/esqueleto.cabal
@@ -4,10 +4,10 @@ cabal-version: 1.12
 --
 -- see: https://github.com/sol/hpack
 --
--- hash: 3a3f42ca57c8ee2f4d01724057ff86b8867202c138e6f03cd8c23000da1fbaa3
+-- hash: c68a1e254e29c461cbf88a8a32c039563f3576cf439b9d947cb3d8dd3916e0e8
 
 name:           esqueleto
-version:        2.6.0
+version:        2.6.1
 synopsis:       Type-safe EDSL for SQL queries on persistent backends.
 description:    @esqueleto@ is a bare bones, type-safe EDSL for SQL queries that works with unmodified @persistent@ SQL backends.  Its language closely resembles SQL, so you don't have to learn new concepts, just new syntax, and it's fairly easy to predict the generated SQL and optimize it for your backend. Most kinds of errors committed when writing SQL are caught as compile-time errors---although it is possible to write type-checked @esqueleto@ queries that fail at runtime.
                 .
diff --git a/package.yaml b/package.yaml
index 5090929..d3825be 100644
--- a/package.yaml
+++ b/package.yaml
@@ -1,5 +1,5 @@
 name: esqueleto
-version: '2.6.0'
+version: 2.6.1
 synopsis: Type-safe EDSL for SQL queries on persistent backends.
 description: ! '@esqueleto@ is a bare bones, type-safe EDSL for SQL queries
   that works with unmodified @persistent@ SQL backends.  Its