search

vshn / espejo

OpenShift and Kubernetes Object Syncer
BSD 3-Clause "New" or "Revised" License
11 stars 2 forks source link

fix(deps): update module github.com/go-logr/logr to v0.4.0 #82

Closed renovate[bot] closed 3 years ago

renovate[bot] commented 3 years ago

WhiteSource Renovate

This PR contains the following updates:

Package Type Update Change
github.com/go-logr/logr require minor v0.1.0 -> v0.4.0

Release Notes

go-logr/logr ### [`v0.4.0`](https://togithub.com/go-logr/logr/releases/v0.4.0) [Compare Source](https://togithub.com/go-logr/logr/compare/v0.3.0...v0.4.0) - Adds `logr.WithCallDepth()` - Deprecate logr/testing.NullLogger in favor of logr.Discard() ### [`v0.3.0`](https://togithub.com/go-logr/logr/releases/v0.3.0) [Compare Source](https://togithub.com/go-logr/logr/compare/v0.2.1...v0.3.0) - Adds support for `NewContext`, `FromContext`, and `FromContextOrDiscard` - Documents the "underlier" pattern for implementations ### [`v0.2.1`](https://togithub.com/go-logr/logr/releases/v0.2.1) [Compare Source](https://togithub.com/go-logr/logr/compare/v0.2.0...v0.2.1) - Adds an `InfoLogger` type alias for v0.1.0 compatibility ### [`v0.2.0`](https://togithub.com/go-logr/logr/releases/v0.2.0) [Compare Source](https://togithub.com/go-logr/logr/compare/v0.1.0...v0.2.0) This tag is API-incompatible with previous versions. - Get rid of `InfoLogger` THIS IS A BREAKING CHANGE - Clarify that `V()` is supposed to be additive

Renovate configuration

:date: Schedule: At any time (no schedule defined).

:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.

:recycle: Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

:no_bell: Ignore: Close this PR and you won't be reminded about this update again.

This PR has been generated by WhiteSource Renovate. View repository job log here.

renovate[bot] commented 3 years ago

Renovate Ignore Notification

As this PR has been closed unmerged, Renovate will now ignore this update (v0.4.0). You will still receive a PR once a newer version is released, so if you wish to permanently ignore this dependency, please add it to the ignoreDeps array of your renovate config.

If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.