From da13603fca01a366a34f55651e4d37ced55c0316 Mon Sep 17 00:00:00 2001 From: Mario Gonzalez Date: Fri, 7 Jul 2023 18:56:22 -0400 Subject: [PATCH] Prepare release 1.3.0 --- pg_backup_api/news.md | 10 ++++++++++ pg_backup_api/news.yml | 10 ++++++++++ pg_backup_api/version.txt | 2 +- 3 files changed, 21 insertions(+), 1 deletion(-) diff --git a/pg_backup_api/news.md b/pg_backup_api/news.md index 89d6ced..be340da 100644 --- a/pg_backup_api/news.md +++ b/pg_backup_api/news.md @@ -2,6 +2,16 @@ © Copyright EnterpriseDB UK Limited 2021-2023 - All rights reserved. +## 1.3.0 (2023-07-13) + +### Notable changes + +- 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.` + ## 1.2.0 (2023-03-29) ### Notable changes diff --git a/pg_backup_api/news.yml b/pg_backup_api/news.yml index 3fb6944..b103a6d 100644 --- a/pg_backup_api/news.yml +++ b/pg_backup_api/news.yml @@ -3,6 +3,16 @@ # pg-backup-api News - History of user-visible changes pg-backup-api release notes: + - version: "1.3.0" + date: "20230713" + changes: + Notable changes: + - 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.` + - version: "1.2.0" date: "20230329" changes: diff --git a/pg_backup_api/version.txt b/pg_backup_api/version.txt index 26aaba0..f0bb29e 100644 --- a/pg_backup_api/version.txt +++ b/pg_backup_api/version.txt @@ -1 +1 @@ -1.2.0 +1.3.0