Skip to content

Commit

Permalink
Prepare release 2.2.0
Browse files Browse the repository at this point in the history
  • Loading branch information
gonzalemario committed Jun 28, 2024
1 parent 4403899 commit 0e47f3c
Show file tree
Hide file tree
Showing 3 changed files with 18 additions and 5 deletions.
14 changes: 10 additions & 4 deletions pg_backup_api/news.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,13 +2,19 @@

© Copyright EnterpriseDB UK Limited 2021-2024 - All rights reserved.

## 2.2.0 (2024-06-29)

### Notable changes

- Functions/methods signatures updates to support Barman >= 3.9

## 2.1.0 (2024-01-25)

### 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)

Expand Down Expand Up @@ -44,8 +50,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)

Expand Down
7 changes: 7 additions & 0 deletions pg_backup_api/news.yml
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,13 @@
# pg-backup-api News - History of user-visible changes

pg-backup-api release notes:
- version: "2.2.0"
date: "20240629"
changes:
Notable changes:
- |
Functions/methods signatures updates to support Barman >= 3.9
- version: "2.1.0"
date: "20240125"
changes:
Expand Down
2 changes: 1 addition & 1 deletion pg_backup_api/version.txt
Original file line number Diff line number Diff line change
@@ -1 +1 @@
2.1.0
2.2.0

0 comments on commit 0e47f3c

Please sign in to comment.