fix(github-release): update cloudnative-pg-source to v1.19.1 #621
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.
This PR contains the following updates:
v1.19.0
->v1.19.1
Release Notes
cloudnative-pg/cloudnative-pg
v1.19.1
Compare Source
Release date: March 20, 2023
Enhancements:
debug
cluster's log level to theinitdb
job (#1503)pg_hba
for the PgBouncer pooler (#1395)psql
command to thecnpg
plugin forkubectl
(#1668) allowing the user to start apsql
session with a pod (the primary by default)Technical enhancements:
--name
option introduced with Barman 3.3 to make the association betwen backups and the object store more robust.Fixes:
status
command of thecnpg
plugin (#1666)nodeAffinity
is applied even ifAdditionalPodAffinity
andAdditionalPodAntiAffinity
are not set (#1663)Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.