From 0c0b42d98b66eb4d28d548d795edcdcf572c2f57 Mon Sep 17 00:00:00 2001
From: Damien Baty <damien@damienbaty.com>
Date: Sun, 20 Sep 2026 08:42:55 +0200
Subject: [PATCH 1/2] docs: Clarify release process

... because I forgot to bump the release number in ``__init__.py``. I
am too used to "zest.releaser".
---
 RELEASES.md | 33 ++++++++++++++++++++++++++++++++-
 1 file changed, 32 insertions(+), 1 deletion(-)

diff --git a/RELEASES.md b/RELEASES.md
index d5bc64035..2553c922e 100644
--- a/RELEASES.md
+++ b/RELEASES.md
@@ -3,4 +3,35 @@ Releasing pgcli
 
 You have been made the maintainer of `pgcli`? Congratulations!
 
-To release a new version of the package, [create a new release](https://github.com/dbcli/pgcli/releases) in Github. This will trigger a Github action which will run all the tests, build the wheel and upload it to PyPI.
\ No newline at end of file
+To release a new version of the package:
+
+1. Set the version number (that should follow SemVer) in
+   `changelog.rst` by turning the "Upcoming" section title into
+   something like "4.7.0 (2026-09-19)" (i.e. the version number
+   followed by the date of the release, most probably today); and add
+   a new empty "Upcoming" section.
+
+2. Set the same version number in `__init__.py`.
+
+3. [Create a new GitHub release](https://github.com/dbcli/pgcli/releases/new):
+
+   1. Click on "Select tag", input the new tag name (it should start
+      with "v", for example "v4.7.0") and click "Create new tag".
+
+   2. Select target branch: `main`.
+
+   3. Input release title: the version number (without "v"), for example
+      "4.7.0".
+
+   4. In the release notes, copy the corresponding section from
+      `changelog.rst`. Double-check the rendered text. Warning:
+      changelog is in reSTructuredText, release notes are in Markdown,
+      syntax is similar but not exactly compatible.
+
+   5. No binary file to upload, default release label ("Latest"), no
+      "discussion for this release".
+
+   6. Click on "Publish release".
+
+   This will trigger a GitHub action that runs all the tests, builds
+   the package and uploads it to PyPI.
\ No newline at end of file

From 4d48743a265a885060aa76bcea77961d6e91fbf6 Mon Sep 17 00:00:00 2001
From: Damien Baty <damien@damienbaty.com>
Date: Sun, 20 Sep 2026 08:45:40 +0200
Subject: [PATCH 2/2] release: Prepare for 4.7.1 release

---
 changelog.rst     | 12 ++++++++++++
 pgcli/__init__.py |  2 +-
 2 files changed, 13 insertions(+), 1 deletion(-)

diff --git a/changelog.rst b/changelog.rst
index 8c4e03756..83e0ac390 100644
--- a/changelog.rst
+++ b/changelog.rst
@@ -2,10 +2,22 @@ Upcoming
 ========
 
 
+4.7.1 (2026-09-20)
+==================
+
+Bug fixes:
+----------
+* Fix wrong version number that was shown in `pgcli --version` for
+  version 4.7.0.
+
 
 4.7.0 (2026-09-19)
 ==================
 
+**Brown bag release:** this version shows (in `pgcli --version`) as
+"4.6.0" instead of "4.7.0".
+
+
 Features:
 ---------
 * Add support for `single-command` to run a SQL command and exit.
diff --git a/pgcli/__init__.py b/pgcli/__init__.py
index db01fb213..cc72154c1 100644
--- a/pgcli/__init__.py
+++ b/pgcli/__init__.py
@@ -1 +1 @@
-__version__ = "4.6.0"
+__version__ = "4.7.1"