docs: Update release notes for 5.0.1

Author: natemcmaster

.claude/skills/prepare-release/SKILL.md

@@ -23,16 +23,20 @@ Run git commands to analyze commits since last release:
 - `git log --grep` for PR merges
 - Look for conventional commit patterns: `fix:`, `feat:`, `break:`, `docs:`, etc.
 
-### 3. Categorize Changes
+### 3. Filter and Categorize Changes
 
-Group into categories (in this order):
+**Exclude from release notes:**
+- Dependabot / automated dependency bump commits (e.g., `chore(deps): Bump ...`). These are routine maintenance and not user-facing.
+- CI/tooling-only changes (e.g., updating GitHub Actions workflows, claude workflows) unless they affect the shipped package.
+
+Group remaining changes into categories (in this order):
 
 1. **Breaking changes** (major versions only) - API removals, behavior changes
 2. **Features** - New functionality or APIs
 3. **Fixes** - Bug fixes and corrections
 4. **Improvements** - Performance or usability enhancements
 5. **Docs** - Documentation-only changes
-6. **Other** - Infrastructure, tooling, CI/CD
+6. **Other** - Infrastructure, tooling, CI/CD (only if user-facing or noteworthy)
 
 ### 4. Generate releasenotes.props Entry
 
@@ -57,15 +61,31 @@ Fixes:
 ```
 
 **Patch versions:**
+
+Append the patch notes directly at the end of the existing parent version's `StartsWith('X.Y.')` block. Do NOT create a separate conditional block. Add the patch section just before the closing `</PackageReleaseNotes>` tag of the parent version:
+
 ```xml
-<PackageReleaseNotes Condition="'$(VersionPrefix)' == 'X.Y.Z'">
-$(PackageReleaseNotes)
+<PackageReleaseNotes Condition="$(VersionPrefix.StartsWith('X.Y.'))">
+...existing X.Y.0 release notes...
 
-X.Y.Z patch:
+Updates in X.Y.Z patch:
 * @user: fix description (#123)
 </PackageReleaseNotes>
 ```
 
+For multiple patches, append each one in order at the end of the same block:
+
+```xml
+...existing X.Y.0 release notes...
+
+Updates in X.Y.1 patch:
+* @user: fix description (#123)
+
+Updates in X.Y.2 patch:
+* @user: another fix (#456)
+</PackageReleaseNotes>
+```
+
 ### 5. Generate CHANGELOG.md Entry
 
 **Format:** `* [@contributor]: description ([#PR])`
@@ -196,10 +216,7 @@ See https://natemcmaster.github.io/CommandLineUtils/vX.0/upgrade-guide.html
 
 ### Patch Versions
 
-Use `$(PackageReleaseNotes)` to inherit parent version's notes.
-
-For first patch (X.Y.1), create new conditional entry after parent.
-For subsequent patches, add BEFORE existing patches but AFTER minor version.
+Append patch notes directly into the existing parent version's `StartsWith('X.Y.')` block in `releasenotes.props`. Do NOT create a separate conditional block or use `$(PackageReleaseNotes)` inheritance. Each patch gets an "Updates in X.Y.Z patch:" section appended at the end of the parent block.
 
 ## Quality Checklist
 

CHANGELOG.md

@@ -1,5 +1,12 @@
 # Changelog
 
+## [v5.0.1](https://github.com/natemcmaster/CommandLineUtils/compare/v5.0.0...v5.0.1)
+
+### Features
+* [@sensslen]: Restore target framework compilation for .NET Framework ([#591])
+
+[#591]: https://github.com/natemcmaster/CommandLineUtils/pull/591
+
 ## [v5.0.0](https://github.com/natemcmaster/CommandLineUtils/compare/v4.1.1...v5.0.0)
 
 ### Breaking changes

README.md

@@ -138,3 +138,15 @@ If you need help with this project, please ...
 
 This is a fork of [Microsoft.Extensions.CommandLineUtils](https://github.com/aspnet/Common), which was [completely abandoned by Microsoft](https://github.com/aspnet/Common/issues/257). This project [forked in 2017](https://github.com/natemcmaster/CommandLineUtils/commit/f039360e4e51bbf8b8eb6236894b626ec7944cec) and continued to make improvements. From 2017 to 2021, over 30 contributors added new features and fixed bugs. As of 2022, the project has entered maintenance mode, so no major changes are planned. [See this issue for details on latest project status.](https://github.com/natemcmaster/CommandLineUtils/issues/485) This project is not abandoned -- I believe this library provides a stable API and rich feature set good enough for most developers to create command line apps in .NET -- but only the most critical of bugs will be fixed (such as security issues).
 
+## Supported .NET Versions
+
+Framework      | Version | Reason
+---------------|---------|--------------------
+`dotnet`       | 8.0     | Lowest Microsoft LTS version at time of release. See <https://endoflife.date/dotnet>
+.NET Framework | 4.7.2   | Lowest .NET Framework version fully compatible with [.NET Standard 2.0][netstandard-guidance]
+
+_Why not directly compile for .NET Standard?_
+
+Microsoft guidance says ".NET 5 and later versions adopt a different approach to establishing uniformity that eliminates the need for .NET Standard in most scenarios." Compiling for 2 frameworks appears to be sufficient, so we avoid added complexity.
+
+[netstandard-guidance]: https://learn.microsoft.com/en-us/dotnet/standard/net-standard?tabs=net-standard-2-0

src/CommandLineUtils/releasenotes.props

@@ -26,6 +26,9 @@ Other:
 * @natemcmaster: Use NuGet trusted publishing with OIDC
 * @dependabot: Update GitHub Actions (#568)
 * @natemcmaster: Upgrade docfx to 2.78.4
+
+Updates in 5.0.1 patch:
+* @sensslen: Restore target framework compilation for .NET Framework (#591)
     </PackageReleaseNotes>
     <PackageReleaseNotes Condition="$(VersionPrefix.StartsWith('4.1.'))">
 Changes since 4.0: