Releases: bombsimon/logrusr
Releases · bombsimon/logrusr
v4.1.0
What's Changed
- With call depth additive by @bombsimon in #28
- Add support for
logr.Marshaler
by @bombsimon in #29
Full Changelog: v4.0.0...v4.1.0
v4.0.0
v3.1.0
What's Changed
- Fix parallel invocation and also a couple typos per the spellchecker. by @binaryphile in #20
- Remove one frame from the default call depth by @bombsimon in #21
- Fix GitHub actions by @bombsimon in #22
New Contributors
- @binaryphile made their first contribution in #20
Full Changelog: v3.0.0...v3.1.0
v3.0.0
What's Changed
- Update logr to v1.2.2 and update go.mod to 1.17 by @aledbf in #8
- README.md: Replace NewLogger with New by @cfergeau in #9
- Update CI, supported versions and README by @bombsimon in #10
- Map V-level logging to logrus named logging by @bombsimon in #13
- Stop overwriting logger on struct when adding fields by @bombsimon in #14
- Simplify severity logging by @bombsimon in #15
- Don't create logger in each test case by @bombsimon in #16
- V3 release by @bombsimon in #17
New Contributors
Full Changelog: v2.0.1...v3.0.0
v2.0.1
v2.0.0
v1.1.0
Fix race condition that existed since we didn't create a copy of the logger. Now every modifying method will create a clone, this means
V()
WithName()
WithValues()
This is almost a breaking change since the behavior of the logger changes, although this seems like the expected behavior based on logrus
, it's the expected behavior in the tests and the expected behavior in the examples. I settled on only bumping the minor version hoping that this will not have a negative effect to anyone.