How to make a psycopg release#
Check if there is a new version or libpq or OpenSSL; in such case update
LIBPQ_VERSION
and/orOPENSSL_VERSION
in.github/workflows/packages-bin.yml
.Check if there is a new cibuildwheel release; if so, upgrade it in
.github/workflows/packages-bin.yml
.Use
tools/bump_version.py
to upgrade package version numbers.Push to GitHub to run the tests workflow.
Build the packages by triggering manually the ones requested among:
Delete the
wheelhouse
directory there is one.Build m1 packages by running
./tools/build/run_build_macos_arm64.sh BRANCH
. On successful completion it will save built packages inwheelhouse
If all packages were built ok, push the new tag created by
bump_version.py
:git push --tags
Download the
artifacts.zip
package from the last Packages workflow run.Unpack the packages in the wheelhouse dir:
mkdir -p wheelhouse cd wheelhouse unzip ~/Downloads/artifact.zip
If the package is a testing one, upload it on TestPyPI with:
$ twine upload -r testpypi *
If the package is stable, omit
-r testpypi
:$ twine upload *
Run
tools/bump_version.py -l dev
to bump to the next dev version.
When a new PostgreSQL major version is released#
Add the new version to
tools/update_errors.py
and run the script to add new error classes.Run the script
tools/update_oids.py
to add new oids. Use-h
to get an example docker command line to run a server locally.Bump
PG_VERSION
in themacos
job of.github/workflows/packages-bin.yml
.Bump
pg_version
intools/build/build_macos_arm64.sh
.Bump the version in
tools/build/wheel_win32_before_build.bat
.