-
Notifications
You must be signed in to change notification settings - Fork 133
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support Serilog 3.0.0 #222
Labels
feature-request
A feature should be added or improved.
module/logging
p2
This is a standard priority issue
queued
Comments
Xilconic
added
feature-request
A feature should be added or improved.
needs-triage
This issue or PR still needs to be triaged.
labels
Jun 20, 2023
Thanks for submitting feature request. This needs review with the team. |
ashishdhingra
added
needs-review
and removed
needs-triage
This issue or PR still needs to be triaged.
labels
Jun 20, 2023
Needs reproduction if our HLL has issues when customer upgrades to |
ashishdhingra
added
p2
This is a standard priority issue
queued
and removed
needs-review
labels
Jun 23, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
feature-request
A feature should be added or improved.
module/logging
p2
This is a standard priority issue
queued
Describe the feature
Serilog 3.0.0 has been released on June 20th 1:01 AM GMT+2. Changelog: https://github.com/serilog/serilog/releases/tag/v3.0.0
AWS.Logger.SeriLog
currently supports Serilog v2.6.0 and up.The major version release of Serilog does come with breaking changes.
Use Case
Aiming to keep up with current developments in dependencies we use, to security minimize risks and benefiting from performance improvements.
Proposed Solution
Update the dependency on Serilog to version 3.0.0 and fix breaking changes.
Other Information
No response
Acknowledgements
AWS .NET SDK and/or Package version used
AWS.Logger.SeriLog v3.2.0
Targeted .NET Platform
.NET6
Operating System and version
AmazonLinux, Windows 10
The text was updated successfully, but these errors were encountered: