From f8086ec36e9b8407ca57b32551d08a811eab4f5d Mon Sep 17 00:00:00 2001 From: parsonsmatt Date: Wed, 5 May 2021 15:52:21 -0600 Subject: [PATCH] changelog, vbump --- changelog.md | 6 ++++++ esqueleto.cabal | 2 +- 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/changelog.md b/changelog.md index 03a58ed..b6b9a83 100644 --- a/changelog.md +++ b/changelog.md @@ -1,3 +1,9 @@ +3.4.2.1 +======= +- @parsonsmatt + - [#245](https://github.com/bitemyapp/esqueleto/pull/245) + - Support `persistent-2.13` + 3.4.2.0 ======= - @parsonsmatt diff --git a/esqueleto.cabal b/esqueleto.cabal index 22986c8..4a7c434 100644 --- a/esqueleto.cabal +++ b/esqueleto.cabal @@ -1,7 +1,7 @@ cabal-version: 1.12 name: esqueleto -version: 3.4.2.0 +version: 3.4.2.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. .