Prepare for release 2.2

[hashworks]

• Add CHANGELOG entry for the release
• Update version number throughout
• Update version related tests

Loosely followed the previous #1017.

[hashworks]

Feel free to delay this for additional PRs and tests. I'll update the changelog as needed.

[dimitri]

Thanks for preparing the release. Please have a look at #1019 and more importantly how to test for upgrades. Then test for upgrades using packages, if you have time to do that.

If I remember correctly the idea was to use patch updates (2.1.1, 2.1.2, etc) when the monitor schema does not change, and minor updates (2.1 to 2.2, etc) for “bigger” updates with monitor schema change. The recent versions we published warranted a version number change of the “minor update” fashion, but did not change the monitor schema. We still need empty schema upgrade files.

[hashworks]

We still need empty schema upgrade files.

I've taken the liberty to cherry-pick e3a6da8 and added a 2.1 -> 2.2 schema upgrade file.

Closes #1019.

[hashworks]

Please have a look at #1019 and more importantly how to test for upgrades. Then test for upgrades using packages, if you have time to do that.

I'll see what I can do.

[dimitri]

I'll see what I can do.

See the README at https://github.com/hapostgres/pg_auto_failover/tree/main/tests/upgrade where I documented the process I used to follow before releasing new versions.