Skip to content
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

Release 7.0.0 #562

Merged
merged 15 commits into from
Sep 9, 2024
Merged

Release 7.0.0 #562

merged 15 commits into from
Sep 9, 2024

Conversation

ckadluba
Copy link
Member

@ckadluba ckadluba commented Sep 9, 2024

ckadluba and others added 15 commits August 29, 2024 14:38
Update serilog v3.1.1 to 4.0.0
Update Microsoft.Data.SqlClient to 5.2.1
PerioadingBatching moved to batching in serilog core.
* Removed null checks in config extensions if sink factory returns null before calling Sink() method from Serilog's LoggerSinkConfiguration or LoggerAuditSinkConfiguration. The truth is that our sink factory may not return null. If it does in production, we should let the exception happen. It happened in the tests because of a missing setup on two mocks.
* Added missing setups in tests.
Bumped major version after Serilog update from 3 to 4.
Update serilog to 4 and move batching to Serilog core (fixed tests)
Prepared package validation in Serilog.Sinks.MSSqlServer.csproj. Not activated yet because it must be disabled during a major version release because there is not yet a base release to compare with on nuget.org.
Added DEVELOPMENT.md. Yet it has only info about how to create a release of the sink.
* Let Build.ps1 and release.yml run on an ubuntu agent
* Full automatic release: use last commit message (usually merge commit from PR) as release description
…mation

Package validation release automation
@github-advanced-security
Copy link

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

@ckadluba ckadluba merged commit 39d0888 into main Sep 9, 2024
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants