chore(deps): bump barman version to 3.20.0 - #1090
Merged
Merged
Conversation
mnencia
reviewed
Aug 31, 2026
litaocdl
force-pushed
the
dev/bump-barman-version
branch
4 times, most recently
from
September 1, 2026 05:59
bbe792e to
1790b8f
Compare
Contributor
Author
|
all the gcs test failed due to issue EnterpriseDB/barman#1218 |
litaocdl
force-pushed
the
dev/bump-barman-version
branch
2 times, most recently
from
September 1, 2026 14:03
eb5cbea to
6c8a74f
Compare
hh24k
reviewed
Sep 2, 2026
hh24k
approved these changes
Sep 2, 2026
Signed-off-by: Tao Li <tao.li@enterprisedb.com>
Co-authored-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com> Signed-off-by: Tao Li <tao.li@enterprisedb.com>
Signed-off-by: Tao Li <tao.li@enterprisedb.com>
Signed-off-by: Tao Li <tao.li@enterprisedb.com>
litaocdl
force-pushed
the
dev/bump-barman-version
branch
from
September 2, 2026 06:29
6c8a74f to
3200573
Compare
mnencia
changed the title
Deleting the GCS Entry() calls dropped e2e coverage permanently and left the GCS factory types and fakegcsserver.go referenced nowhere. Ginkgo's --fail-on-pending forbids Pending/XEntry, but a runtime Skip() inside the shared spec body avoids that check while keeping the factories wired up, making it easier to notice and re-enable the tests once EnterpriseDB/barman#1218 is fixed. Signed-off-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com>
mnencia
approved these changes
Sep 2, 2026
The lockfile had drifted to a Python 3.12 header, not matching the python3.13 venv the sidecar image ships. Regenerated with the correct Python version (see #1093 for the task that automates this going forward); the barman==3.20.0 pin and hashes are unchanged. Signed-off-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com>
mnencia
force-pushed
the
dev/bump-barman-version
branch
from
September 2, 2026 14:16
65ca0c2 to
fa8ae2e
Compare
NiccoloFei
approved these changes
Sep 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bump barman to 3.20.0 and regenerate the sidecar's pip lockfile with the same Python 3.13 used by the sidecar's venv.
barman 3.20.0 dropped fake-gcs-server support (EnterpriseDB/barman#1218), so the GCS backup/restore and replica-cluster e2e specs are skipped at runtime until that's fixed upstream.
Also bundles tar into the sidecar image: barman 3.20.0's restore path now shells out to it, and the distroless base doesn't ship it.