Skip to content

Clarify release documentation + prepare for 4.7.1 release #1644

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dbaty merged 2 commits into from
Sep 20, 2026
+45 −2
Merged

Clarify release documentation + prepare for 4.7.1 release #1644

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0c0b42d
docs: Clarify release process
dbaty Sep 20, 2026
4d48743
release: Prepare for 4.7.1 release
dbaty Sep 20, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
33 changes: 32 additions & 1 deletion RELEASES.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
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.
12 changes: 12 additions & 0 deletions changelog.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
2 changes: 1 addition & 1 deletion pgcli/__init__.py
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1 +1 @@
__version__ = "4.6.0"
__version__ = "4.7.1"
Loading