From 6786962aa072f4e53b3346a67d67cc6e8b02b1a9 Mon Sep 17 00:00:00 2001
From: Mario Gonzalez <mario.gonzalez@enterprisedb.com>
Date: Thu, 11 Sep 2025 12:17:35 -0300
Subject: [PATCH] Prepare release 2.2.0

---
 pg_backup_api/news.md     | 15 +++++++++++----
 pg_backup_api/news.yml    |  8 ++++++++
 pg_backup_api/version.txt |  2 +-
 3 files changed, 20 insertions(+), 5 deletions(-)

diff --git a/pg_backup_api/news.md b/pg_backup_api/news.md
index 5d2a827..c2594cf 100644
--- a/pg_backup_api/news.md
+++ b/pg_backup_api/news.md
@@ -2,6 +2,13 @@
 
 © Copyright EnterpriseDB UK Limited 2021-2025 - All rights reserved.
 
+## 2.2.0 (2025-09-12)
+
+### Notable changes
+
+- The location of the barman conf file can now be specified by using
+  the PG_BACKUP_API_BARMAN_CONF environment variable.
+
 ## 2.1.1 (2024-06-29)
 
 ### Buxfixes
@@ -13,8 +20,8 @@
 ### Notable changes
 
 - Barman now supports changes in the configuration whilst it's running. This
-  pg-backup-api release adds the required endpoints to trigger that switch
-  when requested.
+  pg-backup-api release adds the required endpoints to trigger that switch when
+  requested.
 
 ## 2.0.0 (2023-10-03)
 
@@ -50,8 +57,8 @@
 - Ability to parse and recognise Barman shortcuts like `latest` or `oldest`.
 
 - Access to barman-api.log is now only required when running under a WSGI
-  server. This means pg-backup-api commands like status will no longer fail
-  if they are executed by a user that cannot access barman-api.log.`
+  server. This means pg-backup-api commands like status will no longer fail if
+  they are executed by a user that cannot access barman-api.log.`
 
 ## 1.2.0 (2023-03-29)
 
diff --git a/pg_backup_api/news.yml b/pg_backup_api/news.yml
index 5a3253d..e6e9812 100644
--- a/pg_backup_api/news.yml
+++ b/pg_backup_api/news.yml
@@ -3,6 +3,14 @@
 # pg-backup-api News - History of user-visible changes
 
 pg-backup-api release notes:
+  - version: "2.2.0"
+    date: "20250912"
+    changes:
+      Notable changes:
+        - |
+          The location of the barman conf file can now be specified by using
+          the PG_BACKUP_API_BARMAN_CONF environment variable.
+
   - version: "2.1.1"
     date: "20240629"
     changes:
diff --git a/pg_backup_api/version.txt b/pg_backup_api/version.txt
index 3e3c2f1..ccbccc3 100644
--- a/pg_backup_api/version.txt
+++ b/pg_backup_api/version.txt
@@ -1 +1 @@
-2.1.1
+2.2.0