prepare changes for new release

Mostly list of changes, new version number was already commited earlier. Also I noticed another place (in META.json) where the minimum version of postgresql needed to be updated.

META.json

@@ -24,7 +24,7 @@
    "prereqs": {
       "runtime": {
          "requires": {
-            "PostgreSQL": "9.4.0"
+            "PostgreSQL": "9.5.0"
          }
       }
    },

doc/pg_repack.rst

@@ -40,7 +40,7 @@ Requirements
 ------------
 
 PostgreSQL versions
-    PostgreSQL 9.5, 9.6, 10, 11, 12, 13, 14, 15, 16.
+    PostgreSQL 9.5, 9.6, 10, 11, 12, 13, 14, 15, 16, 17.
 
     PostgreSQL 9.4 and before it are not supported.
 
@@ -476,6 +476,19 @@ Creating indexes concurrently comes with a few caveats, please see `the document
 Releases
 --------
 
+* pg_repack 1.5.1
+
+  * Added support for PostgreSQL 17
+  * Fix wrong OID format type in repack_trigger (issue #380)
+  * Fix check of NOT NULL by repack.primary_keys (issue #282)
+  * Fixed processing of tablespace names requiring quoted identifiers (issue #386)
+  * Replace ``PQconnectdb()`` by ``PQconnectdbParams()`` (issue #382)
+  * Added ``--apply-count`` option (issue #392)
+  * Do not include a declaratively partitioned table with option ``--only-indexes`` (issue #389)
+  * Fix possible two vacuums concurrently processing the same relfilenode (issue #399)
+  * Use savepoints when retrying to take AccessShareLock (issue #383)
+  * Fix swap of relfrozenxid, relfrozenxid and relallvisible (issue #377, #157)
+
 * pg_repack 1.5.0
 
   * Added support for PostgreSQL 16

doc/pg_repack_jp.rst

@@ -62,7 +62,7 @@ pg_repackでは再編成する方法として次のものが選択できます
   ------------
   
   PostgreSQL versions
-      PostgreSQL 9.5, 9.6, 10, 11, 12, 13, 14, 15, 16.
+      PostgreSQL 9.5, 9.6, 10, 11, 12, 13, 14, 15, 16, 17.
   
       PostgreSQL 9.4 and before it are not supported.
   
@@ -77,7 +77,7 @@ pg_repackでは再編成する方法として次のものが選択できます
 ---------
 
 PostgreSQL バージョン
-    PostgreSQL 9.5, 9.6, 10, 11, 12, 13, 14, 15, 16
+    PostgreSQL 9.5, 9.6, 10, 11, 12, 13, 14, 15, 16, 17
 
 ディスク
     テーブル全体の再編成を行うには、対象となるテーブルと付属するインデックスのおよそ2倍のサイズのディスク空き容量が必要です。例えば、テーブルとインデックスを合わせたサイズが1GBの場合、2GBのディスク領域が必要となります。