From c536762063d039db2feb1b56a6f142ed2aa199cb Mon Sep 17 00:00:00 2001 From: Florian Wermelinger Date: Fri, 26 Jan 2024 14:49:59 +0100 Subject: [PATCH 1/2] updated sonarAnalyzer and changelog --- CHANGELOG.md | 4 ++++ Neolution.CodeAnalysis.TestsRuleset.nuspec | 2 +- Neolution.CodeAnalysis.nuspec | 2 +- 3 files changed, 6 insertions(+), 2 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 98d1bee..14ec3c5 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -7,6 +7,10 @@ and adheres to a project-specific [Versioning](/README.md). ## [Unreleased] +### Changed + +- Updated SonarAnalyzer to version 9 because of new .Net8 language features that otherwise cause false positives + ## [3.0.5] - 2023-09-28 ### Fixed diff --git a/Neolution.CodeAnalysis.TestsRuleset.nuspec b/Neolution.CodeAnalysis.TestsRuleset.nuspec index f25a7d1..8aa70c8 100644 --- a/Neolution.CodeAnalysis.TestsRuleset.nuspec +++ b/Neolution.CodeAnalysis.TestsRuleset.nuspec @@ -13,7 +13,7 @@ true - + diff --git a/Neolution.CodeAnalysis.nuspec b/Neolution.CodeAnalysis.nuspec index 10de2f1..277dd03 100644 --- a/Neolution.CodeAnalysis.nuspec +++ b/Neolution.CodeAnalysis.nuspec @@ -13,7 +13,7 @@ true - + From 47f982c7bf13f384cd03820e62359a717b2fe5fc Mon Sep 17 00:00:00 2001 From: Florian Wermelinger Date: Fri, 26 Jan 2024 15:59:37 +0100 Subject: [PATCH 2/2] Added release instructions to Readme.md (cherry picked from commit 0fd03f808bee667d49e4dfcb7bcaaa16b9e3a2b5) --- README.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 99af239..2095e6d 100644 --- a/README.md +++ b/README.md @@ -23,4 +23,11 @@ Given a version number `MAJOR.MINOR.PATCH`, an incremented number for: ### What it means in practice: - You can (and should) always update the package to the latest `PATCH` version whenever you have the chance to do it, it should never break the build. - Updating to the latest `MINOR` version can break the build and may require minor refactorings. But you can expect to have Roslyn code fixes and/or documentation available for the changes that are needed to fix the build. -- `MAJOR` updates will break your build and may require major refactorings. \ No newline at end of file +- `MAJOR` updates will break your build and may require major refactorings. + + +## How to create a new release +- Create a new branch for example feature/remove-some-rule +- Update the CHANGELOG.md file with your changes according to keepachangelog.com +- Go to github and create a new release. There you can define the new version number and release stage +- The github action will create a new nuget package and push it to nuget.org \ No newline at end of file