V9.0.10/service pack #127

gimlichael · 2025-10-17T12:03:01Z

This pull request updates the release notes for multiple NuGet packages to document the new version 9.0.10. The main focus is on updating dependencies to their latest versions in alignment with the supported Target Framework Monikers (TFMs). No code changes are included—these are documentation updates reflecting maintenance and dependency management.

Key changes:

Release notes and dependency updates:

Bumped version numbers to 9.0.10 and updated the "Availability" section to reflect supported TFMs (.NET 9, .NET 8, and in some cases .NET Standard 2.0) in all affected PackageReleaseNotes.txt files. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20]
Added a note in each release note file under "ALM" stating that dependencies have been changed to the latest and greatest with respect to TFMs, indicating proactive dependency management for all NuGet packages. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20]

Summary by CodeRabbit

New Features
- Added SHA512/256 cryptography support.
Chores
- Released version 9.0.10 with .NET 9 support.
- Updated package dependencies to latest versions.
- Modernized test infrastructure.

coderabbitai · 2025-10-17T12:03:29Z

Walkthrough

Version 9.0.10 release preparation: adds version 9.0.10 entries across 40+ NuGet package release notes files with updated availability and dependency change notes, updates Directory.Packages.props with .NET 9.0.10 and test SDK versions, removes a test platform package reference from build configuration, updates test environment Docker image, and adds changelog entry.

Changes

Cohort / File(s)	Summary
NuGet Package Release Notes `.nuget/Cuemon.AspNetCore.App/PackageReleaseNotes.txt`, `.nuget/Cuemon.AspNetCore.Authentication/PackageReleaseNotes.txt`, `.nuget/Cuemon.AspNetCore.Mvc/PackageReleaseNotes.txt`, `.nuget/Cuemon.AspNetCore.Razor.TagHelpers/PackageReleaseNotes.txt`, `.nuget/Cuemon.AspNetCore/PackageReleaseNotes.txt`, `.nuget/Cuemon.Core.App/PackageReleaseNotes.txt`, `.nuget/Cuemon.Core/PackageReleaseNotes.txt`, `.nuget/Cuemon.Data.Integrity/PackageReleaseNotes.txt`, `.nuget/Cuemon.Data.SqlClient/PackageReleaseNotes.txt`, `.nuget/Cuemon.Data/PackageReleaseNotes.txt`, `.nuget/Cuemon.Diagnostics/PackageReleaseNotes.txt`, `.nuget/Cuemon.Extensions.AspNetCore.Authentication/PackageReleaseNotes.txt`, `.nuget/Cuemon.Extensions.AspNetCore.Mvc.Formatters.Text.Json/PackageReleaseNotes.txt`, `.nuget/Cuemon.Extensions.AspNetCore.Mvc.Formatters.Xml/PackageReleaseNotes.txt`, `.nuget/Cuemon.Extensions.AspNetCore.Mvc.RazorPages/PackageReleaseNotes.txt`, `.nuget/Cuemon.Extensions.AspNetCore.Mvc/PackageReleaseNotes.txt`, `.nuget/Cuemon.Extensions.AspNetCore.Text.Json/PackageReleaseNotes.txt`, `.nuget/Cuemon.Extensions.AspNetCore.Xml/PackageReleaseNotes.txt`, `.nuget/Cuemon.Extensions.AspNetCore/PackageReleaseNotes.txt`, `.nuget/Cuemon.Extensions.Collections.Generic/PackageReleaseNotes.txt`, `.nuget/Cuemon.Extensions.Collections.Specialized/PackageReleaseNotes.txt`, `.nuget/Cuemon.Extensions.Core/PackageReleaseNotes.txt`, `.nuget/Cuemon.Extensions.Data.Integrity/PackageReleaseNotes.txt`, `.nuget/Cuemon.Extensions.Data/PackageReleaseNotes.txt`, `.nuget/Cuemon.Extensions.DependencyInjection/PackageReleaseNotes.txt`, `.nuget/Cuemon.Extensions.Diagnostics/PackageReleaseNotes.txt`, `.nuget/Cuemon.Extensions.Hosting/PackageReleaseNotes.txt`, `.nuget/Cuemon.Extensions.IO/PackageReleaseNotes.txt`, `.nuget/Cuemon.Extensions.Net/PackageReleaseNotes.txt`, `.nuget/Cuemon.Extensions.Reflection/PackageReleaseNotes.txt`, `.nuget/Cuemon.Extensions.Runtime.Caching/PackageReleaseNotes.txt`, `.nuget/Cuemon.Extensions.Text.Json/PackageReleaseNotes.txt`, `.nuget/Cuemon.Extensions.Text/PackageReleaseNotes.txt`, `.nuget/Cuemon.Extensions.Threading/PackageReleaseNotes.txt`, `.nuget/Cuemon.Extensions.Xml/PackageReleaseNotes.txt`, `.nuget/Cuemon.IO/PackageReleaseNotes.txt`, `.nuget/Cuemon.Net/PackageReleaseNotes.txt`, `.nuget/Cuemon.Resilience/PackageReleaseNotes.txt`, `.nuget/Cuemon.Runtime.Caching/PackageReleaseNotes.txt`, `.nuget/Cuemon.Security.Cryptography/PackageReleaseNotes.txt`, `.nuget/Cuemon.Threading/PackageReleaseNotes.txt`, `.nuget/Cuemon.Xml/PackageReleaseNotes.txt`	Adds version 9.0.10 release entry with availability for .NET 9, .NET 8 (and .NET Standard 2.0 for applicable packages) and ALM note: "CHANGED Dependencies to latest and greatest with respect to TFMs". Some files also reorder or remove duplicate dependency change notes from prior versions.
Build Configuration `Directory.Build.props`	Removes conditional package reference to Microsoft.TestPlatform.ObjectModel for test projects targeting net4 on Linux.
Centralized Package Versions `Directory.Packages.props`	Bumps dependency versions: Backport.System.Threading.Lock 3.1.4 → 3.1.5, Codebelt.Extensions.Xunit and related packages 10.0.5 → 10.0.6, Microsoft.NET.Test.Sdk 17.14.1 → 18.0.0, xunit.runner.visualstudio 3.1.4 → 3.1.5; upgrades .NET 9 packages (Microsoft.Data.Sqlite, Microsoft.Extensions.DependencyInjection, Microsoft.Extensions.Hosting, Microsoft.Extensions.Http, Microsoft.Extensions.Options.ConfigurationExtensions) to 9.0.10; updates Microsoft.Data.Sqlite (net8/net9 group) 8.0.19 → 8.0.20 and Microsoft.Data.SqlClient 6.1.1 → 6.1.2.
Test Environment Configuration `testenvironments.json`	Updates Docker test environment image tag from `gimlichael/ubuntu-testrunner:mono-net8.0.414-9.0.305` to `gimlichael/ubuntu-testrunner:mono-net8.0.415-9.0.306`.
Release Documentation `CHANGELOG.md`	Adds changelog entry for version 9.0.10 (2025-10-17) noting it is a service update focusing on package dependencies.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

gimlichael/Cuemon#126: Sequential service update (v9.0.9 → v9.0.10) with identical release notes and dependency changes.
gimlichael/Cuemon#125: Performs the same package/version/TFM updates across release notes and configuration files.
gimlichael/Cuemon#119: Coordinated version and dependency bumps with updates to the same release notes and Directory.Packages.props files.

Suggested reviewers

TheAsteroid

Poem

🐰 A rabbit hops through version lands,
Where dependencies shift in planned commands,
Nine-zero-ten now leads the way,
With fresher packages every day,
Tests updated, configs aligned—
A service release, refined! 🌟

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The pull request title "V9.0.10/service pack" directly aligns with the primary change in the changeset. The raw summary shows that across all modified files, the core objective is releasing version 9.0.10 as a service pack focused on package dependency updates, which is confirmed by the CHANGELOG.md entry stating "This is a service update that focuses on package dependencies." The title is concise, specific to both the version number and release type, and uses appropriate versioning conventions that make the primary purpose immediately clear to reviewers scanning the pull request history.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests (beta)

Create PR with unit tests
Post copyable unit tests in a comment
Commit unit tests in branch v9.0.10/service-pack

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

coderabbitai

Actionable comments posted: 0

🧹 Nitpick comments (19)

.nuget/Cuemon.Runtime.Caching/PackageReleaseNotes.txt (1)

5-5: Consider simplifying recurring phrasing across the file (follow-up improvement).

The phrase "with respect to TFMs" appears consistently throughout this file (and likely across other release notes files in the same update). While not a blocking issue, consider using shorter alternatives like "for" or "regarding" in a follow-up pass to improve readability across all versions.
.nuget/Cuemon.Extensions.IO/PackageReleaseNotes.txt (1)
5-5: Consider shortening the phrasing in the ALM note.

The phrase "with respect to TFMs" appears throughout the file and can be tightened for brevity. Consider alternatives like "for TFMs" or "per TFMs."

Example refinement:
-  - CHANGED Dependencies to latest and greatest with respect to TFMs
+  - CHANGED Dependencies to latest and greatest per TFMs
Note: This is a stylistic suggestion based on static analysis; apply it if your documentation guidelines prefer concise phrasing.
.nuget/Cuemon.Extensions.Diagnostics/PackageReleaseNotes.txt (1)

5-5: Minor: Consider more concise phrasing for the ALM note.

The phrase "with respect to TFMs" is slightly wordy and appears consistently across all release entries. Consider simplifying to "for TFMs" or "with TFMs" to improve brevity, though this is a minor style matter and the current phrasing is acceptable.

.nuget/Cuemon.Xml/PackageReleaseNotes.txt (1)

5-5: Consider simplifying the phrase "with respect to TFMs."

The phrase "with respect to TFMs" is used consistently throughout all version entries (9 occurrences in this file alone). Since this PR updates 40+ release notes files per the summary, consider using a shorter alternative like "for TFMs" or "regarding TFMs" for better conciseness across the entire documentation update. This would be a good opportunity to standardize the language across all affected files if you're making coordinated updates.

Also applies to: 11-11, 17-17, 23-23, 29-29, 35-35, 41-41, 47-47, 53-53, 59-59, 65-65

.nuget/Cuemon.Extensions.Data.Integrity/PackageReleaseNotes.txt (1)

1-5: ✓ New 9.0.10 entry is consistent and correctly positioned.

The new release notes entry follows the established pattern across all existing versions in the file. Availability (.NET 9, .NET 8, and .NET Standard 2.0) aligns with other 9.0.x releases, and the ALM note appropriately documents the dependency update.

Optional future improvement: The phrasing "with respect to TFMs" appears consistently throughout the file (and presumably across the 40+ NuGet packages in this PR). While static analysis suggests it may be wordy, changing it here would require consistency updates across all versions. Consider this for a future documentation pass if a broader style refactor is undertaken.

.nuget/Cuemon.Threading/PackageReleaseNotes.txt (1)

5-5: Optional: Consider shortening the ALM note phrasing.

The phrase "with respect to TFMs" is used consistently throughout the file and is perfectly acceptable. However, static analysis suggests this could be more concise. Since this pattern appears throughout the document, any improvement would require updating multiple entries. This can be deferred as a future documentation polish task.
.nuget/Cuemon.Extensions.AspNetCore.Mvc.RazorPages/PackageReleaseNotes.txt (2)
80-80: Fix inconsistent version declaration format.

Version identifiers use mixed formatting: some lines have a colon after "Version" (lines 80, 86, 92: Version: 8.x.x) while others don't (lines 1, 7, 13, etc.: Version 9.x.x). Standardize to one format for consistency.

Apply one of these diffs depending on your preferred format:

Option 1: Remove colons to match 9.x entries
-Version: 8.1.0
+Version 8.1.0
-Version: 8.0.1
+Version 8.0.1
-Version: 8.0.0
+Version 8.0.0
Option 2: Add colons to all entries to match 8.0.x style
-Version 9.0.10
+Version: 9.0.10
-Version 9.0.9
+Version: 9.0.9
(and so on for all 9.x entries)
Also applies to: 86-86, 92-92

5-5: Simplify "with respect to TFMs" phrasing.

The phrase "with respect to TFMs" appears repeatedly throughout the release notes (9+ occurrences). Consider replacing it with more concise language such as:

"to latest versions for supported TFMs"

"to align with current TFMs"

"for current TFM support"

This improves readability without losing meaning.

Example diff for lines 5, 11, 17, 23, etc.:
-- CHANGED Dependencies to latest and greatest with respect to TFMs
+- CHANGED Dependencies to latest versions for supported TFMs
Also applies to: 11-11, 17-17, 23-23, 29-29, 35-35, 41-41, 47-47, 53-53, 59-59, 65-65, 78-78, 84-84, 90-90, 98-98
.nuget/Cuemon.Security.Cryptography/PackageReleaseNotes.txt (1)
5-5: Consider more concise phrasing for the ALM dependency note.

The phrase "with respect to TFMs" is flagged by static analysis as wordy. It appears identically across all version blocks. Consider using a more concise alternative such as "for TFMs" or simply "to TFMs" to improve readability and consistency.

For example, replace:
- CHANGED Dependencies to latest and greatest with respect to TFMs
+ CHANGED Dependencies to latest and greatest for TFMs
Also applies to: 11-11, 17-17, 23-23, 29-29, 35-35, 49-49, 55-55, 61-61, 67-67, 73-73, 86-86, 92-92, 98-98, 105-105
.nuget/Cuemon.Extensions.AspNetCore.Authentication/PackageReleaseNotes.txt (1)

1-6: Documentation pattern is consistent and clear.

The version 9.0.10 entry follows the established format with clear availability and ALM information.

Consider simplifying the phrasing "with respect to TFMs" to reduce verbosity—alternatives like "for TFMs" or "targeting TFMs" are more concise.

.nuget/Cuemon.Extensions.Threading/PackageReleaseNotes.txt (1)

1-6: Documentation is consistent with TFM support profile.

Version 9.0.10 entry correctly includes .NET Standard 2.0 in Availability alongside .NET 9 and .NET 8.

Same optional simplification suggested for other files: the phrase "with respect to TFMs" could be more concise.

.nuget/Cuemon.Extensions.AspNetCore.Mvc.Formatters.Xml/PackageReleaseNotes.txt (1)

1-6: Good! The 9.0.10 release notes block is well-structured and consistent with the PR pattern.

The changes preserve all existing version history and clearly communicate the dependency update. One optional improvement: consider shortening "with respect to TFMs" to "for TFMs" or "regarding TFMs" for conciseness, though the current phrasing is idiomatic in release notes.

.nuget/Cuemon.Extensions.Hosting/PackageReleaseNotes.txt (1)

1-6: Consider simplifying the wording in the ALM dependency note.

The phrase "with respect to TFMs" in line 5 is flagged as potentially wordy. Consider alternatives like "for TFMs," "matching TFMs," or "with TFM support" for cleaner, more concise release notes. This wording appears across multiple release note files in the PR, so a targeted update would improve consistency and readability throughout the suite.

Additionally, the same dependency note appears in both the 9.0.10 block (line 5) and the 9.0.9 block (line 11 below). Clarify whether this duplication is intentional for historical context or if 9.0.9 should be updated to omit it.

.nuget/Cuemon.Extensions.AspNetCore.Mvc.Formatters.Text.Json/PackageReleaseNotes.txt (1)

1-6: Apply consistent wording improvements across all release note files.

As with the previous file, the phrase "with respect to TFMs" should be simplified for clarity and conciseness. The same pattern and recommendation applies here.

.nuget/Cuemon.Resilience/PackageReleaseNotes.txt (1)

1-6: Simplify the wording of the ALM dependency note across all files.

The phrase "with respect to TFMs" is flagged by static analysis as wordy. Refactor to a concise alternative such as "for TFMs," "matching TFMs," or "in TFM support." Since this pattern repeats across 40+ release note files in this PR, a bulk refactor would improve consistency and readability.

.nuget/Cuemon.Extensions.Xml/PackageReleaseNotes.txt (1)

1-6: Consider simplifying the ALM note for clarity and conciseness.

The ALM note uses colloquial language ("latest and greatest") combined with the wordy phrase "with respect to." This phrasing appears consistently across multiple release notes files.

Suggestion: Simplify to one of these alternatives:

"CHANGED Dependencies to latest versions for supported TFMs"

"CHANGED Dependencies to latest compatible versions"

"UPDATED Dependencies across all supported target frameworks"

The static analysis tool also flagged "with respect to" as potentially wordy; these alternatives maintain clarity while reducing verbosity.

.nuget/Cuemon.AspNetCore.Razor.TagHelpers/PackageReleaseNotes.txt (1)

1-6: Availability statement is appropriately scoped for ASP.NET Core package.

The restriction to .NET 9 and .NET 8 (no .NET Standard) is correct for ASP.NET Core packages. However, the ALM note uses the same wordy phrasing noted in the previous file. Apply the same simplification suggestion across all files for consistency.

CHANGELOG.md (1)

1-11: Overall PR documentation consistency check.

Systematic issue across all 7 release notes files: The ALM notes repeatedly use "with respect to TFMs," which LanguageTool flagged as wordy phrasing combined with colloquial "latest and greatest" language.

Recommendation: Standardize ALM note wording across all 40+ files to one of these alternatives:

"CHANGED Dependencies to latest versions for supported TFMs"

"UPDATED All dependencies to latest compatible versions"

"CHANGED Dependencies to latest releases across target frameworks"

This improves readability and professionalism, especially for public-facing release notes. While not a blocker, consistency and clarity matter for end-user documentation.

.nuget/Cuemon.Extensions.Net/PackageReleaseNotes.txt (1)

1-6: Consistent format maintained for version 9.0.10 entry.

The new release notes follow the established pattern from previous versions. However, note that versions 9.0.1 through 9.0.10 all contain identical release notes ("CHANGED Dependencies to latest and greatest with respect to TFMs"). While consistent, this provides limited value to users trying to understand what specifically changed between versions.

Consider including more specific details in future release notes, such as:

Which dependencies were updated (package names and version ranges)

Any notable fixes or improvements from dependency updates

Breaking changes, if any

Note: The static analysis hint about "with respect to" being wordy applies to all historical entries. Changing only the new entry would create inconsistency, so this is best left as-is or addressed globally in a separate effort.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1102195 and 40188cf.

📒 Files selected for processing (46)

.nuget/Cuemon.AspNetCore.App/PackageReleaseNotes.txt (1 hunks)
.nuget/Cuemon.AspNetCore.Authentication/PackageReleaseNotes.txt (1 hunks)
.nuget/Cuemon.AspNetCore.Mvc/PackageReleaseNotes.txt (1 hunks)
.nuget/Cuemon.AspNetCore.Razor.TagHelpers/PackageReleaseNotes.txt (1 hunks)
.nuget/Cuemon.AspNetCore/PackageReleaseNotes.txt (1 hunks)
.nuget/Cuemon.Core.App/PackageReleaseNotes.txt (1 hunks)
.nuget/Cuemon.Core/PackageReleaseNotes.txt (1 hunks)
.nuget/Cuemon.Data.Integrity/PackageReleaseNotes.txt (1 hunks)
.nuget/Cuemon.Data.SqlClient/PackageReleaseNotes.txt (1 hunks)
.nuget/Cuemon.Data/PackageReleaseNotes.txt (1 hunks)
.nuget/Cuemon.Diagnostics/PackageReleaseNotes.txt (1 hunks)
.nuget/Cuemon.Extensions.AspNetCore.Authentication/PackageReleaseNotes.txt (1 hunks)
.nuget/Cuemon.Extensions.AspNetCore.Mvc.Formatters.Text.Json/PackageReleaseNotes.txt (1 hunks)
.nuget/Cuemon.Extensions.AspNetCore.Mvc.Formatters.Xml/PackageReleaseNotes.txt (1 hunks)
.nuget/Cuemon.Extensions.AspNetCore.Mvc.RazorPages/PackageReleaseNotes.txt (1 hunks)
.nuget/Cuemon.Extensions.AspNetCore.Mvc/PackageReleaseNotes.txt (1 hunks)
.nuget/Cuemon.Extensions.AspNetCore.Text.Json/PackageReleaseNotes.txt (1 hunks)
.nuget/Cuemon.Extensions.AspNetCore.Xml/PackageReleaseNotes.txt (1 hunks)
.nuget/Cuemon.Extensions.AspNetCore/PackageReleaseNotes.txt (1 hunks)
.nuget/Cuemon.Extensions.Collections.Generic/PackageReleaseNotes.txt (1 hunks)
.nuget/Cuemon.Extensions.Collections.Specialized/PackageReleaseNotes.txt (1 hunks)
.nuget/Cuemon.Extensions.Core/PackageReleaseNotes.txt (1 hunks)
.nuget/Cuemon.Extensions.Data.Integrity/PackageReleaseNotes.txt (1 hunks)
.nuget/Cuemon.Extensions.Data/PackageReleaseNotes.txt (1 hunks)
.nuget/Cuemon.Extensions.DependencyInjection/PackageReleaseNotes.txt (1 hunks)
.nuget/Cuemon.Extensions.Diagnostics/PackageReleaseNotes.txt (1 hunks)
.nuget/Cuemon.Extensions.Hosting/PackageReleaseNotes.txt (1 hunks)
.nuget/Cuemon.Extensions.IO/PackageReleaseNotes.txt (1 hunks)
.nuget/Cuemon.Extensions.Net/PackageReleaseNotes.txt (1 hunks)
.nuget/Cuemon.Extensions.Reflection/PackageReleaseNotes.txt (1 hunks)
.nuget/Cuemon.Extensions.Runtime.Caching/PackageReleaseNotes.txt (1 hunks)
.nuget/Cuemon.Extensions.Text.Json/PackageReleaseNotes.txt (1 hunks)
.nuget/Cuemon.Extensions.Text/PackageReleaseNotes.txt (1 hunks)
.nuget/Cuemon.Extensions.Threading/PackageReleaseNotes.txt (1 hunks)
.nuget/Cuemon.Extensions.Xml/PackageReleaseNotes.txt (1 hunks)
.nuget/Cuemon.IO/PackageReleaseNotes.txt (1 hunks)
.nuget/Cuemon.Net/PackageReleaseNotes.txt (1 hunks)
.nuget/Cuemon.Resilience/PackageReleaseNotes.txt (1 hunks)
.nuget/Cuemon.Runtime.Caching/PackageReleaseNotes.txt (1 hunks)
.nuget/Cuemon.Security.Cryptography/PackageReleaseNotes.txt (1 hunks)
.nuget/Cuemon.Threading/PackageReleaseNotes.txt (1 hunks)
.nuget/Cuemon.Xml/PackageReleaseNotes.txt (1 hunks)
CHANGELOG.md (1 hunks)
Directory.Build.props (0 hunks)
Directory.Packages.props (2 hunks)
testenvironments.json (1 hunks)

💤 Files with no reviewable changes (1)

Directory.Build.props

🧰 Additional context used

🪛 LanguageTool

.nuget/Cuemon.Extensions.Data/PackageReleaseNotes.txt

[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.9 Availability: .NET...