Prepare release 2.4.0

Changelog.md

@@ -1,8 +1,8 @@
 # Changelog
 
-## [Unreleased]
+## [2.4.0] - 2024-05-20
 
-A major update for `PreparedStatement`'s API and multiple renames.
+A major update for `PreparedStatement`'s API, multiple renames.
 
 ### Added
  * `$resultTypes` argument for `Connection::prepare()` and `PreparedStatement::__construct()` 
@@ -268,4 +268,4 @@ Initial release on GitHub
 [2.2.0]: https://github.com/sad-spirit/pg-wrapper/compare/v2.1.1...v2.2.0
 [2.3.0-beta]: https://github.com/sad-spirit/pg-wrapper/compare/v2.2.0...v2.3.0-beta
 [2.3.0]: https://github.com/sad-spirit/pg-wrapper/compare/v2.3.0-beta..v2.3.0
-[Unreleased]: https://github.com/sad-spirit/pg-wrapper/compare/v2.3.0..HEAD
+[2.4.0]: https://github.com/sad-spirit/pg-wrapper/compare/v2.3.0..v2.4.0

README.md

@@ -104,7 +104,7 @@ APIs that we can use with the native extension and / or adds another level of co
 
 * PDO does not expose [`pg_query_params()`](http://php.net/manual/en/function.pg-query-params.php), so you have
   to `prepare()` / `execute()` each query even if you `execute()` it only once. Doctrine DBAL has `Connection::executeQuery()`
-  but it has PDO's `prepare()` / `execute()` under the hood.
+  but it uses `prepare()` / `execute()` under the hood.
 * Postgres only supports `$1` positional parameters natively, while PDO has positional `?` and named `:foo` parameters.
   PDO actually rewrites the query to convert the latter to the former, which ([before PHP 7.4](https://wiki.php.net/rfc/pdo_escape_placeholders)) 
   prevented using [Postgres operators containing `?`](https://www.postgresql.org/docs/current/functions-json.html#FUNCTIONS-JSONB-OP-TABLE) with