fix(deps): update all non-major go dependencies #27
Conversation
This file contains 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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
requested review from
fcanovai,
gbartolini,
leonardoce,
mnencia and
phisco
as code owners
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
sxd
previously approved these changes
Jul 2, 2024
renovate
bot
force-pushed
the
renovate/all-non-major-go-dependencies
branch
from
cf33ca3 to
acac33d
Compare
fcanovai
force-pushed
the
renovate/all-non-major-go-dependencies
branch
from
91e630d to
378f37b
Compare
| datasource | package | from | to | | ---------- | ----------------------------------------------- | ------------------------------------- | ---------------------------------- | | go | github.com/cloudnative-pg/cloudnative-pg | v1.22.1-0.20240123130737-a22a155b9eb8 | v1.23.2 | | go | github.com/cloudnative-pg/cnpg-i | v0.0.0-20240124144003-4c0a1ac46426 | v0.0.0-20240702073529-2ad7cc75560e | | go | github.com/go-logr/logr | v1.3.0 | v1.4.2 | | go | github.com/go-logr/zapr | v1.2.4 | v1.3.0 | | go | github.com/grpc-ecosystem/go-grpc-middleware/v2 | v2.0.1 | v2.1.0 | | go | github.com/snorwin/jsonpatch | v1.4.0 | v1.5.0 | | go | github.com/spf13/cobra | v1.8.0 | v1.8.1 | | go | github.com/spf13/viper | v1.14.0 | v1.19.0 | | go | go.uber.org/zap | v1.26.0 | v1.27.0 | | go | google.golang.org/grpc | v1.60.1 | v1.64.0 | | go | k8s.io/api | v0.28.4 | v0.30.2 | Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Renovate can create commits with lines over the default limit. We change commitlint config to give a warning instead of an error. Signed-off-by: Francesco Canovai <[email protected]>
fcanovai
force-pushed
the
renovate/all-non-major-go-dependencies
branch
from
378f37b to
85228da
Compare
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
fcanovai
approved these changes
Jul 2, 2024
sxd
approved these changes
Jul 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.22.1-0.20240123130737-a22a155b9eb8->v1.23.24c0a1ac->2ad7cc7v1.3.0->v1.4.2v1.2.4->v1.3.0v2.0.1->v2.1.0v1.4.0->v1.5.0v1.8.0->v1.8.1v1.14.0->v1.19.0v1.26.0->v1.27.0v1.60.1->v1.64.0v0.28.4->v0.30.2Release Notes
cloudnative-pg/cloudnative-pg (github.com/cloudnative-pg/cloudnative-pg)
v1.23.2Compare Source
Release date: Jun 12, 2024
Enhancements:
Enabled configuration of standby-sensitive parameters during recovery using a physical backup (#4564)
Enabled the configuration of the liveness probe timeout via the
.spec.livenessProbeTimeoutoption (#4719)cnpgplugin forkubectl:--coloroption, which acceptsalways,never, andauto(default) as values (#4775)Fixes:
Prevented fenced instances from entering an unnecessary loop and consuming all available CPU (#4625)
Resolved an issue where the instance manager on the primary would indefinitely wait for the instance to start after encountering a failure following a stop operation (#4434)
Fixed an issue where the interaction between
hot_standby_feedbackand managed cluster-level replication slots was preventing the autovacuum from operating correctly; this issue was causing disk space to remain occupied by dead tuples (#4811)Fixed a panic in the backup controller that occurred when pod container statuses were missing (#4765)
Prevented unnecessary shutdown of the instance manager (#4670)
Prevented unnecessary reloads of PostgreSQL configuration when unchanged (#4531)
Prevented unnecessary reloads of the ident map by ensuring a consistent and unique method of writing its content (#4648)
Avoided conflicts during phase registration by patching the status of the resource instead of updating it (#4637)
Implemented a timeout when restarting PostgreSQL and lifting fencing (#4504)
Ensured that a replica cluster is restarted after promotion to properly set the archive mode (#4399)
Removed an unneeded concurrent keep-alive routine that was causing random failures in volume snapshot backups (#4768)
Ensured correct parsing of the additional rows field returned when the
pgaudit.log_rowsoption was enabled, preventing audit logs from being incorrectly routed to the normal log stream (#4394)cnpgplugin forkubectl:cnpg statuscommand (#4530)Changes
v1.23.1Compare Source
Release date: Apr 29, 2024
Fixes:
PodMonitorresources, which was failing due to a regression (#4286)v1.23.0Compare Source
Release date: Apr 24, 2024
!!! Important "Important changes to Community Supported Versions" We've updated our support policy to streamline our focus on one supported minor release at a time, rather than two. Additionally, we've extended the supplementary support period for the previous minor release to 3 months.
Features:
ClusterImageCatalogandImageCatalogCRDs to manage operand container images based on PostgreSQL major version. This is facilitated through theCluster's.spec.imageCatalogRef stanza. This feature provides an alternative to the imageName option and will eventually replace it as the default method to define operand container images.replicationSlots.synchronizeReplicas..spec.enablePDBfield to disable PDBs on the primary instance, allowing proper eviction of the pod during maintenance operations. This is particularly useful for single-instance deployments. This feature is intended to replace the node maintenance window feature.Enhancements:
wal_log_hintsPostgreSQL parameter (#4218) (#4218)statuscommand to show the status of PDBs (#4319)barman-cloud-wal-restoreinrecoverybootstrap (#4101)Fixes:
PGDATAin case of failure of the restore job (#4151)cnpgplugin forkubectl:destroy,fencing, andpromoteplugin commands (#4280)cnpg status(#4131)sync-sequencescommand (#4346)Changes:
gcr.io/distroless/static-debian12:nonroot(#4201)v1.22.4Compare Source
Release date: Jun 12, 2024
!!! Warning Version 1.22 is approaching its End-of-Life (EOL) on Jul 24, 2024. If you haven't already, please begin planning for an upgrade promptly to ensure continued support and security.
Enhancements:
Enabled configuration of standby-sensitive parameters during recovery using a physical backup (#4564)
Enabled the configuration of the liveness probe timeout via the
.spec.livenessProbeTimeoutoption (#4719)cnpgplugin forkubectl:--coloroption, which acceptsalways,never, andauto(default) as values (#4775)Fixes:
Prevented fenced instances from entering an unnecessary loop and consuming all available CPU (#4625)
Resolved an issue where the instance manager on the primary would indefinitely wait for the instance to start after encountering a failure following a stop operation (#4434)
Fixed an issue where the interaction between
hot_standby_feedbackand managed cluster-level replication slots was preventing the autovacuum from operating correctly; this issue was causing disk space to remain occupied by dead tuples (#4811)Fixed a panic in the backup controller that occurred when pod container statuses were missing (#4765)
Prevented unnecessary shutdown of the instance manager (#4670)
Prevented unnecessary reloads of PostgreSQL configuration when unchanged (#4531)
Prevented unnecessary reloads of the ident map by ensuring a consistent and unique method of writing its content (#4648)
Avoided conflicts during phase registration by patching the status of the resource instead of updating it (#4637)
Implemented a timeout when restarting PostgreSQL and lifting fencing (#4504)
Ensured that a replica cluster is restarted after promotion to properly set the archive mode (#4399)
Removed an unneeded concurrent keep-alive routine that was causing random failures in volume snapshot backups (#4768)
Ensured correct parsing of the additional rows field returned when the
pgaudit.log_rowsoption was enabled, preventing audit logs from being incorrectly routed to the normal log stream (#4394)cnpgplugin forkubectl:cnpg statuscommand (#4530)Changes
v1.22.3Compare Source
Release date: Apr 24, 2024
Enhancements:
wal_log_hintsPostgreSQL parameter (#4218) (#4218)barman-cloud-wal-restoreinrecoverybootstrap (#4101)Fixes:
PGDATAin case of failure of the restore job (#4151)cnpgplugin forkubectl:destroy,fencing, andpromoteplugin commands (#4280)cnpg status(#4131)sync-sequencescommand (#4346)Changes:
v1.22.2Compare Source
Release date: Mar 14, 2024
Enhancements
wal_levelGUC in PostgreSQL (#4020)cnpg.io/skipWalArchivingannotation to disable WAL archiving when set toenabled(#4055)cnpgplugin forkubectlwith thepublicationandsubscriptioncommand groups to imperatively set up PostgreSQL native logical replication (#4052)CERTIFICATE_DURATIONandEXPIRING_CHECK_THRESHOLDfor automated management of TLS certificates handled by the operator (#3686)cnpgplugin forkubectl(#3875)Fixes
wal_sender_timeoutwhen cloning a replica to prevent timeout errors due to slow connections (#4080)Security
Roleinstead ofClusterRolefor operator permissions in OLM, requiring fewer privileges when installed on a per-namespace basis (#3855, #3990)Changes
--server-sideoption by default when installing the operator (#3729).go-logr/logr (github.com/go-logr/logr)
v1.4.2Compare Source
What's Changed
Dependencies:
Full Changelog: go-logr/logr@v1.4.1...v1.4.2
v1.4.1Compare Source
What's Changed
Full Changelog: go-logr/logr@v1.4.0...v1.4.1
v1.4.0Compare Source
This release dramatically improves interoperability with Go's
log/slogpackage. In particular,logr.NewContextandlogr.NewContextWithSlogLoggeruse the same context key, which allowslogr.FromContextandlogr.FromContextAsSlogLoggerto returnlogr.Loggeror*slog.Loggerrespectively, including transparently converting each to the other as needed.Functions
logr/slogr.NewLograndlogr/slogr.ToSlogHandlerhave been superceded bylogr.FromSlogHandlerandlogr.ToSlogHandlerrespectively, and typelogr/slogr.SlogSinkhas been superceded bylogr.SlogSink. All of the old names inlogr/slogrremain, for compatibility.Package
logr/funcrnow supportslogr.SlogSink, meaning that it's output passes all but one of the Slog conformance tests (that exception being thatfuncrhandles the timestamp itself).Users who have a
logr.Loggerand need a*slog.Loggercan callslog.New(logr.ToSlogHandler(...))and all output will go through the same stack.Users who have a
*slog.Loggerorslog.Handlercan calllogr.FromSlogHandler(...)and all output will go through the same stack.What's Changed
New Contributors
Full Changelog: go-logr/logr@v1.3.0...v1.4.0
go-logr/zapr (github.com/go-logr/zapr)
v1.3.0Compare Source
This release adds support for slog. zapr implements
slogr.SlogSinkand therefore can be used throughslogr.NewSlogHandleras backend for slog.What's Changed
New Contributors
Full Changelog: go-logr/zapr@v1.2.4...v1.3.0
grpc-ecosystem/go-grpc-middleware (github.com/grpc-ecosystem/go-grpc-middleware/v2)
v2.1.0Compare Source
What's Changed
InitializeMetricssignature to allow use withxds.GRPCServerby @bozaro in https://github.com/grpc-ecosystem/go-grpc-middleware/pull/689New Contributors
Full Changelog: grpc-ecosystem/go-grpc-middleware@v2.0.1...v2.1.0
snorwin/jsonpatch (github.com/snorwin/jsonpatch)
v1.5.0Compare Source
Features
float32andfloat64(#13). Thanks @johanneswuerbach, @maribowman, and @igor-plotnikov for your inputs and contributions.Bug fixes
(None)
spf13/cobra (github.com/spf13/cobra)
v1.8.1Compare Source
✨ Features
🐛 Bug fixes
🔧 Maintenance
🧪 Testing & CI/CD
✏️ Documentation
New Contributors
Thank you everyone who contributed to this release and all your hard work! Cobra and this community would never be possible without all of you!!!! 🐍
Full Changelog: spf13/cobra@v1.8.0...v1.8.1
spf13/viper (github.com/spf13/viper)
v1.19.0Compare Source
What's Changed
Bug Fixes 🐛
Dependency Updates ⬆️
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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.