From 3cfd69f1e0a3573237f3d3570375e5e68f64417d Mon Sep 17 00:00:00 2001 From: FantasticFiasco Date: Sun, 10 Mar 2024 23:06:19 +0100 Subject: [PATCH] wip --- CHANGELOG.md | 17 ++++++++++++++--- appveyor.yml | 4 ++-- 2 files changed, 16 insertions(+), 5 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index f2dee0a4..a0822b5c 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -9,10 +9,21 @@ This project adheres to [Semantic Versioning](http://semver.org/) and is followi ### :zap: Added - Support for .NET Framework 4.6.2 +- [#262](https://github.com/FantasticFiasco/serilog-sinks-http/issues/262) [BREAKING CHANGE] Support specifying `flushOnClose` when creating the sink, thus adding the support to suppress sending unsent log events to the log server before closing the sink (proposed by [@murlidakhare](https://github.com/murlidakhare), [@julichan](https://github.com/julichan), [@janichirag11](https://github.com/janichirag11) & [@prasadpaul53](https://github.com/prasadpaul53)) + + **Migration guide** + + The parameter `flushOnClose` has been introduced to the methods `Http`, `DurableHttpUsingFileSizeRolledBuffers` and `DurableHttpUsingTimeRolledBuffers`. Please verify that the arguments pass by you to these methods still align with your intentions. + + To automatically mitigate this kind of *new parameter issue* in the future, move from using positional arguments to named arguments. + +### :dizzy: Changed + +- [#262](https://github.com/FantasticFiasco/serilog-sinks-http/issues/262) [BREAKING CHANGE] Method `PostAsync` of interface `IHttpClient` has changed with the introduction of the `CancellationToken` argument. ### :skull: Removed -- [BREAKING CHANGE] Remove support for .NET Framework 4.5, aligning with the [.NET Framework support policy](https://learn.microsoft.com/lifecycle/products/microsoft-net-framework) +- [#253](https://github.com/FantasticFiasco/serilog-sinks-http/issues/253) [BREAKING CHANGE] Remove support for .NET Framework 4.5, aligning with the [.NET Framework support policy](https://learn.microsoft.com/lifecycle/products/microsoft-net-framework) - [BREAKING CHANGE] Remove support for .NET Framework 4.6.1, aligning with the [.NET Framework support policy](https://learn.microsoft.com/lifecycle/products/microsoft-net-framework) ## [9.0.0-beta.1] - 2023-04-12 @@ -25,7 +36,7 @@ This project adheres to [Semantic Versioning](http://semver.org/) and is followi The parameter `levelSwitch` has been introduced to the methods `Http`, `DurableHttpUsingFileSizeRolledBuffers` and `DurableHttpUsingTimeRolledBuffers`. Please verify that the arguments pass by you to these methods still align with your intentions. - To automatically mitigate this kind of *new parameter issue* in the future, move from using positional arguments to named arguments instead. + To automatically mitigate this kind of *new parameter issue* in the future, move from using positional arguments to named arguments. ## [8.0.0] - 2022-04-10 @@ -37,7 +48,7 @@ This project adheres to [Semantic Versioning](http://semver.org/) and is followi The parameter `batchSizeLimitBytes` has been introduced to the methods `Http`, `DurableHttpUsingFileSizeRolledBuffers` and `DurableHttpUsingTimeRolledBuffers`. Please verify that the arguments pass by you to these methods still align with your intentions. - To automatically mitigate this kind of *new parameter issue* in the future, move from using positional arguments to named arguments instead. + To automatically mitigate this kind of *new parameter issue* in the future, move from using positional arguments to named arguments. - [#166](https://github.com/FantasticFiasco/serilog-sinks-http/issues/166) Support for content encoding [Gzip](https://en.wikipedia.org/wiki/Gzip) using HTTP client `JsonGzipHttpClient` (contribution by [@vaibhavepatel](https://github.com/vaibhavepatel), [@KalininAndreyVictorovich](https://github.com/KalininAndreyVictorovich) and [@AntonSmolkov](https://github.com/AntonSmolkov)) - [#166](https://github.com/FantasticFiasco/serilog-sinks-http/issues/166) Support for specifying `HttpClient` when creating `JsonHttpClient` and `JsonGzipHttpClient` diff --git a/appveyor.yml b/appveyor.yml index 9143db78..7181cdd8 100644 --- a/appveyor.yml +++ b/appveyor.yml @@ -24,14 +24,14 @@ deploy: release: Release ${APPVEYOR_REPO_TAG_NAME} description: TODO auth_token: - secure: j02iHBdEdOPrRurPI+J8gxvi153bzB2wMx0k8N4n2M8UyYJioyYYaXHB+318iR+J + secure: 2vpeyFd0qviswr3A0GfM7kVn0byuTAyN2CSAy+WtnT5PRvAG5uQu9IDeG2ikOo97 artifact: NuGet draft: true on: APPVEYOR_REPO_TAG: true - provider: NuGet api_key: - secure: 6wrGpQA9SV1Isu2qpTTmeDfclPSJSbWc7ySeFqRi96Seb0c5LI9Er+e1j+RmeGb2 + secure: rgk0wGra4vfgFPaHVx+TZelydrrsMNXuOYjK2C1JisFFru8fVhW15XY84Pk3uyXq symbol_server: https://www.nuget.org skip_symbols: false on: