Bump log4net to 2.0.17 #1
Open
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.
Updated log4net from 2.0.10 to 2.0.17.
Release notes
Sourced from log4net's releases.
2.0.17
Apache log4net 2.0.17 addresses reported issues:
Bug fixes
Complete diff
2.0.16
A big thanks to @FreeAndNil for doing all the hard work of collating changes.
Bug fixes
Enhancements
2.0.15
Attention: .NET 3.5 Client Profile is no longer supported. I'm really sorry, I've tried to keep as many of the legacy targets available as possible, but after spending another 4 or so hours trying to get net35-client to build on any machine, I've given up - as far as I'm aware, this should only affect Windows XP clients. I'm afraid 2.0.14 was the end of the road for you. Apache log4net 2.0.15 addresses reported issues:
Bug fixes
Enhancements
2.0.14
2.0.13
Some minor updates:
This is essentially the same release as rc-1, with the artifacts updated so that unzipping them won't scatter files in the target.
2.0.12
PlatformNotSupported
exceptions raised on !win32 when attempting to include the current user name in logs.Full Changelog: apache/logging-log4net@rel/2.0.11...rel/2.0.12
2.0.11
What's Changed
Full Changelog: apache/logging-log4net@rel/2.0.10...rel/2.0.11
Commits viewable in compare view.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)