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 8.0.0 #594

Merged
merged 16 commits into from
Oct 31, 2024
Merged

Release 8.0.0 #594

merged 16 commits into from
Oct 31, 2024

Conversation

ckadluba
Copy link
Member

  • Updated to .NET 8
  • Updated nearly all dependencies
  • Improved build script (build samples, fail on vulns, ...)
  • Removed some obsolete vulnerability fix dependencies
  • Fixed missing dependency in AppConfigDemo sample

* Do not use loops since we only have one project for main sink, one for tests and one for perftests.
* Use try-finally blocks to pop back to caller's initial dir on errors.
* Fail the build if there were nuget restore errors (e.g. due to known vulns).
* build also sample projects on PR (skip them in release.yml and perftests.yml).
In the test project the assembly System.Transactions was referenced also for .NET (Core) which leads to a warning with the update to .NET 8. Now we reference it only for the .NET Framework targets.
Necessary to have .NET 4.6.2 reference assemblies for building and analyzing AppConfigDemo.
System.Formats.Asn1 and System.Private.Uri were only added to fix a vulnerability caused by old versions referenced transitively. After the update to .NET 8 and update of all dependencies they can now be removed again.
System.Text.Json was only added to fix a vulnerability caused by an old version referenced transitively. After the update to .NET 8 and update of all dependencies it can now be removed again.
@ckadluba ckadluba added this pull request to the merge queue Oct 31, 2024
Merged via the queue into serilog-mssql:dev with commit 73ef762 Oct 31, 2024
7 checks passed
@ckadluba ckadluba deleted the release-8.0.0 branch October 31, 2024 11:23
@jonorossi
Copy link
Member

If we're dropping support for .NET 6 and 7 (or you have to fallback to .NET Standard), then at some point we should probably drop .NET Framework 4.6.2 and just keep .NET Framework 4.7.2. If you're maintaining your .NET Framework apps then you should be using 4.8.

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