V9.0.1/package maintenance #25
Conversation
WalkthroughThis pull request encompasses a comprehensive update across multiple files, focusing on version upgrades, dependency management, and framework compatibility. The changes primarily involve updating to .NET 9.0, extending copyright years, modifying package dependencies, and refactoring hosting environment interfaces. The modifications span configuration files, package release notes, workflows, and source code, indicating a coordinated effort to modernize and streamline the project's infrastructure and dependencies. Changes
Possibly related PRs
Poem
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (5)
.nuget/Codebelt.Extensions.Xunit.Hosting/PackageReleaseNotes.txt (2)
4-5: Consider rephrasing for clarity.While the meaning is clear, consider simplifying "with respect to TFMs" to "for all target frameworks" for better readability.
-CHANGED Dependencies to latest and greatest with respect to TFMs +CHANGED Dependencies to latest and greatest for all target frameworks🧰 Tools
🪛 LanguageTool
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs
Improvements
- CHANGED Host...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
7-11: Fix grammatical errors in improvement descriptions.The content accurately reflects the changes, but there are minor grammatical issues.
-CHANGED HostFixture class in the Codebelt.Extensions.Xunit.Hosting namespace no longer have a dependency to IHostingEnvironment (TFM netstandard2.0) -CHANGED HostTest class in the Codebelt.Extensions.Xunit.Hosting namespace no longer have a dependency to IHostingEnvironment (TFM netstandard2.0) -CHANGED IHostFixture interface in the Codebelt.Extensions.Xunit.Hosting namespace no longer have a dependency to IHostingEnvironment (TFM netstandard2.0) -CHANGED IHostingEnvironmentTest interface in the Codebelt.Extensions.Xunit.Hosting namespace no longer have a dependency to IHostingEnvironment (TFM netstandard2.0) +CHANGED HostFixture class in the Codebelt.Extensions.Xunit.Hosting namespace no longer has a dependency on IHostingEnvironment (TFM netstandard2.0) +CHANGED HostTest class in the Codebelt.Extensions.Xunit.Hosting namespace no longer has a dependency on IHostingEnvironment (TFM netstandard2.0) +CHANGED IHostFixture interface in the Codebelt.Extensions.Xunit.Hosting namespace no longer has a dependency on IHostingEnvironment (TFM netstandard2.0) +CHANGED IHostingEnvironmentTest interface in the Codebelt.Extensions.Xunit.Hosting namespace no longer has a dependency on IHostingEnvironment (TFM netstandard2.0).nuget/Codebelt.Extensions.Xunit.Hosting.AspNetCore/PackageReleaseNotes.txt (1)
4-5: Enhance the ALM section clarity.Consider these improvements:
- Use more concise language (e.g., "for" instead of "with respect to")
- Add specific version details of updated dependencies
Apply this diff to improve clarity:
-# ALM -- CHANGED Dependencies to latest and greatest with respect to TFMs +# ALM +- UPDATED Dependencies to latest versions for supported TFMs: + - Microsoft.Bcl.AsyncInterfaces + - Microsoft.NET.Test.Sdk + - xunit🧰 Tools
🪛 LanguageTool
[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.0
Availability: ....(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Codebelt.Extensions.Xunit/PackageReleaseNotes.txt (1)
4-5: Enhance ALM section with specific dependency updates.The current ALM section is too vague. Consider:
- Using more precise language (e.g., "for target frameworks" instead of "with respect to TFMs")
- Listing the specific dependencies that were updated with their version changes
Example format:
-# ALM -- CHANGED Dependencies to latest and greatest with respect to TFMs +# ALM +- UPDATED Microsoft.Bcl.AsyncInterfaces to version X.Y.Z +- UPDATED Microsoft.NET.Test.Sdk to version X.Y.Z +- UPDATED xunit to version X.Y.Z🧰 Tools
🪛 LanguageTool
[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.0
Availability: ....(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
CHANGELOG.md (1)
14-15: Important architectural change regarding .NET Standard 2.0.The migration from .NET Standard 2.0 to .NET 8.0 (LTS) is a significant change that improves maintainability but may affect consumers targeting older frameworks.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (15)
.docfx/Dockerfile.docfx(1 hunks).docfx/docfx.json(2 hunks).github/workflows/pipelines.yml(0 hunks).nuget/Codebelt.Extensions.Xunit.Hosting.AspNetCore/PackageReleaseNotes.txt(1 hunks).nuget/Codebelt.Extensions.Xunit.Hosting/PackageReleaseNotes.txt(1 hunks).nuget/Codebelt.Extensions.Xunit/PackageReleaseNotes.txt(1 hunks)CHANGELOG.md(1 hunks)Directory.Build.props(1 hunks)Directory.Packages.props(1 hunks)LICENSE(1 hunks)src/Codebelt.Extensions.Xunit.Hosting/HostFixture.cs(0 hunks)src/Codebelt.Extensions.Xunit.Hosting/HostTest.cs(0 hunks)src/Codebelt.Extensions.Xunit.Hosting/IHostFixture.cs(0 hunks)src/Codebelt.Extensions.Xunit.Hosting/IHostingEnvironmentTest.cs(0 hunks)testenvironments.json(1 hunks)
💤 Files with no reviewable changes (5)
- .github/workflows/pipelines.yml
- src/Codebelt.Extensions.Xunit.Hosting/IHostingEnvironmentTest.cs
- src/Codebelt.Extensions.Xunit.Hosting/HostFixture.cs
- src/Codebelt.Extensions.Xunit.Hosting/HostTest.cs
- src/Codebelt.Extensions.Xunit.Hosting/IHostFixture.cs
✅ Files skipped from review due to trivial changes (4)
- LICENSE
- .docfx/Dockerfile.docfx
- Directory.Build.props
- testenvironments.json
🧰 Additional context used
🪛 LanguageTool
CHANGELOG.md
[style] ~19-~19: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...ns.Xunit updated to latest and greatest with respect to TFMs
- Codebelt.Extensions.Xunit.Hosti...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
[style] ~20-~20: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ....Hosting updated to latest and greatest with respect to TFMs
- Codebelt.Extensions.Xunit.Hosti...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
[style] ~21-~21: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...pNetCore updated to latest and greatest with respect to TFMs
Changed
- HostFixture cl...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Codebelt.Extensions.Xunit.Hosting/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
Improvements
- CHANGED Host...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Codebelt.Extensions.Xunit.Hosting.AspNetCore/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.0
Availability: ....
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Codebelt.Extensions.Xunit/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.0
Availability: ....
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
⏰ Context from checks skipped due to timeout of 90000ms (6)
- GitHub Check: 🧪 Test (windows-2022, Release)
- GitHub Check: 🧪 Test (windows-2022, Debug)
- GitHub Check: 🧪 Test (ubuntu-22.04, Release)
- GitHub Check: 📦 Pack (Release)
- GitHub Check: 🧪 Test (ubuntu-22.04, Debug)
- GitHub Check: 📦 Pack (Debug)
🔇 Additional comments (8)
.nuget/Codebelt.Extensions.Xunit.Hosting/PackageReleaseNotes.txt (1)
1-2: LGTM! Version and availability information is accurate.The version number and framework compatibility align with the PR objectives.
.nuget/Codebelt.Extensions.Xunit.Hosting.AspNetCore/PackageReleaseNotes.txt (1)
1-2: LGTM! Version and availability information is accurate.The version number and framework compatibility information align with the PR objectives.
.nuget/Codebelt.Extensions.Xunit/PackageReleaseNotes.txt (1)
1-2: Verify framework compatibility.Please ensure that the package has been thoroughly tested with .NET 9, as it's a relatively new framework version.
✅ Verification successful
Framework compatibility verified successfully
The package's framework compatibility is properly configured with appropriate multi-targeting, conditional compilation, and framework-specific dependencies for all listed frameworks (.NET 9, .NET 8, and .NET Standard 2.0).
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify framework compatibility settings in project files # Search for TargetFramework settings echo "Checking TargetFramework settings in project files:" fd -e csproj -e props | xargs grep -l "TargetFramework" | while read -r file; do echo "=== $file ===" cat "$file" | grep -A 1 -B 1 "TargetFramework" done # Search for framework-specific conditional compilation echo -e "\nChecking framework-specific conditional compilation:" rg "#if\s+NET9_0|#if\s+NETSTANDARD2_0"Length of output: 4011
Directory.Packages.props (2)
28-33: Framework-specific package updates look consistent.The updates maintain proper versioning across different target frameworks:
- .NET 9: Updated to 9.0.1
- .NET 8 & netstandard2: Using appropriate LTS versions
Also applies to: 35-41
10-24: Package version updates look good, but verify test framework compatibility.The package updates align with .NET 9 compatibility. The xUnit update from 2.9.2 to 2.9.3 and xunit.runner.visualstudio update to 3.0.1 are significant changes.
Let's verify the compatibility of these versions:
✅ Verification successful
✓ Package versions are up-to-date and compatible
All package versions match the latest stable releases on NuGet, including:
- Microsoft.Bcl.AsyncInterfaces 9.0.1
- xunit 2.9.3
- xunit.runner.visualstudio 3.0.1
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Check if these package versions exist and are the latest stable versions for pkg in "Microsoft.Bcl.AsyncInterfaces" "Microsoft.NET.Test.Sdk" "xunit" "xunit.runner.visualstudio"; do echo "Checking $pkg..." curl -s "https://api.nuget.org/v3/registration5-semver1/$pkg/index.json" | jq -r '.items[0].upper' doneLength of output: 1326
Script:
#!/bin/bash # Check specific versions using catalog API for pkg in "Microsoft.Bcl.AsyncInterfaces/9.0.1" "xunit/2.9.3" "xunit.runner.visualstudio/3.0.1"; do echo "Checking $pkg..." curl -s "https://api.nuget.org/v3/catalog0/data/2024.01.01.00.00.00/$pkg.json" | jq -r '.listed' done # Also check latest versions for pkg in "Microsoft.Bcl.AsyncInterfaces" "xunit" "xunit.runner.visualstudio"; do echo "Latest version for $pkg:" curl -s "https://api.nuget.org/v3-flatcontainer/$pkg/index.json" | jq -r '.versions[-1]' doneLength of output: 1922
.docfx/docfx.json (1)
17-17: Documentation configuration updates are aligned with the project changes.The updates correctly reflect:
- Target framework change to net9.0
- Extended copyright year to 2024-2025
Also applies to: 50-50
CHANGELOG.md (2)
10-21: Changelog updates are clear and follow the standard format.The changes are well documented, particularly the important note about updating .NET Standard 2.0 dependencies to .NET 8.0 LTS.
🧰 Tools
🪛 LanguageTool
[style] ~19-~19: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...ns.Xunit updated to latest and greatest with respect to TFMs
- Codebelt.Extensions.Xunit.Hosti...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
[style] ~20-~20: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ....Hosting updated to latest and greatest with respect to TFMs
- Codebelt.Extensions.Xunit.Hosti...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
[style] ~21-~21: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...pNetCore updated to latest and greatest with respect to TFMsChanged
- HostFixture cl...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
25-28: Verify the impact of removing IHostingEnvironment dependency.The removal of IHostingEnvironment dependency from multiple classes needs verification to ensure no breaking changes.
Let's check for any remaining references:
✅ Verification successful
IHostingEnvironment dependency has been properly removed ✅
The codebase correctly uses
IHostEnvironmentin all implementations. The word "HostingEnvironment" only appears in interface names and property identifiers, which don't affect the actual type usage.🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Search for any remaining IHostingEnvironment references echo "Checking for remaining IHostingEnvironment references..." rg -l "IHostingEnvironment" --type-add 'csharp:*.{cs,csproj}' -tcsharp # Check if IHostEnvironment is properly used as replacement echo "Checking for IHostEnvironment usage..." rg -l "IHostEnvironment" --type-add 'csharp:*.{cs,csproj}' -tcsharpLength of output: 747
Script:
#!/bin/bash # Check content of files with IHostingEnvironment references echo "=== IHostFixture.cs ===" rg -C 5 "IHostingEnvironment" src/Codebelt.Extensions.Xunit.Hosting/IHostFixture.cs echo -e "\n=== IHostingEnvironmentTest.cs ===" rg -C 5 "IHostingEnvironment" src/Codebelt.Extensions.Xunit.Hosting/IHostingEnvironmentTest.cs echo -e "\n=== IGenericHostTest.cs ===" rg -C 5 "IHostingEnvironment" src/Codebelt.Extensions.Xunit.Hosting/IGenericHostTest.cs # Check for conditional compilation directives echo -e "\n=== Checking for TFM-related conditional compilation ===" rg "#if.*NETSTANDARD" --type-add 'csharp:*.{cs,csproj}' -tcsharp src/Codebelt.Extensions.Xunit.Hosting/Length of output: 2340
Script:
#!/bin/bash # Check implementation details echo "=== HostFixture.cs implementation ===" rg -C 5 "IHost(ing)?Environment" src/Codebelt.Extensions.Xunit.Hosting/HostFixture.cs echo -e "\n=== HostTest.cs implementation ===" rg -C 5 "IHost(ing)?Environment" src/Codebelt.Extensions.Xunit.Hosting/HostTest.csLength of output: 2664
| Version 9.0.1 | ||
| Availability: .NET 9 and .NET 8 | ||
|
|
||
| # ALM | ||
| - CHANGED Dependencies to latest and greatest with respect to TFMs | ||
|
|
There was a problem hiding this comment.
🛠️ Refactor suggestion
Document breaking changes related to IHostingEnvironment.
The PR includes removal of obsolete IHostingEnvironment code, but this breaking change isn't documented in the release notes. Consider adding a "Breaking Changes" section to inform users about this significant change.
Add this section after the ALM entry:
# ALM
- CHANGED Dependencies to latest and greatest with respect to TFMs
+# Breaking Changes
+- REMOVED Obsolete IHostingEnvironment code in favor of IHostEnvironment📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| Version 9.0.1 | |
| Availability: .NET 9 and .NET 8 | |
| # ALM | |
| - CHANGED Dependencies to latest and greatest with respect to TFMs | |
| Version 9.0.1 | |
| Availability: .NET 9 and .NET 8 | |
| # ALM | |
| - CHANGED Dependencies to latest and greatest with respect to TFMs | |
| # Breaking Changes | |
| - REMOVED Obsolete IHostingEnvironment code in favor of IHostEnvironment |
🧰 Tools
🪛 LanguageTool
[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.0
Availability: ....
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #25 +/- ##
==========================================
+ Coverage 85.58% 85.86% +0.27%
==========================================
Files 31 31
Lines 680 672 -8
Branches 84 84
==========================================
- Hits 582 577 -5
+ Misses 95 92 -3
Partials 3 3 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (3)
CHANGELOG.md (3)
14-16: Consider adding migration steps for .NET Standard 2.0 to .NET 8.0 transition.While the important note about updating dependencies is helpful, users might benefit from specific migration steps or considerations when moving from .NET Standard 2.0 to .NET 8.0.
Would you like me to help draft migration guidance for this transition?
19-21: Improve clarity in dependency updates.The phrase "with respect to TFMs" is wordy and could be clearer. Consider a more direct phrasing.
-Codebelt.Extensions.Xunit updated to latest and greatest with respect to TFMs -Codebelt.Extensions.Xunit.Hosting updated to latest and greatest with respect to TFMs -Codebelt.Extensions.Xunit.Hosting.AspNetCore updated to latest and greatest with respect to TFMs +Codebelt.Extensions.Xunit updated to align with new Target Framework Monikers +Codebelt.Extensions.Xunit.Hosting updated to align with new Target Framework Monikers +Codebelt.Extensions.Xunit.Hosting.AspNetCore updated to align with new Target Framework Monikers🧰 Tools
🪛 LanguageTool
[style] ~19-~19: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...ns.Xunit updated to latest and greatest with respect to TFMs
- Codebelt.Extensions.Xunit.Hosti...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
[style] ~20-~20: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ....Hosting updated to latest and greatest with respect to TFMs
- Codebelt.Extensions.Xunit.Hosti...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
[style] ~21-~21: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...pNetCore updated to latest and greatest with respect to TFMsChanged
- HostFixture cl...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
25-28: Consider grouping related changes.The removal of IHostingEnvironment dependency is listed separately for each class/interface. Consider consolidating these related changes for better readability.
-HostFixture class in the Codebelt.Extensions.Xunit.Hosting namespace no longer have a dependency to IHostingEnvironment (TFM netstandard2.0) -HostTest class in the Codebelt.Extensions.Xunit.Hosting namespace no longer have a dependency to IHostingEnvironment (TFM netstandard2.0) -IHostFixture interface in the Codebelt.Extensions.Xunit.Hosting namespace no longer have a dependency to IHostingEnvironment (TFM netstandard2.0) -IHostingEnvironmentTest interface in the Codebelt.Extensions.Xunit.Hosting namespace no longer have a dependency to IHostingEnvironment (TFM netstandard2.0) +Removed IHostingEnvironment dependency (TFM netstandard2.0) from the following types in Codebelt.Extensions.Xunit.Hosting namespace: + - HostFixture class + - HostTest class + - IHostFixture interface + - IHostingEnvironmentTest interface
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
CHANGELOG.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
CHANGELOG.md
[style] ~19-~19: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...ns.Xunit updated to latest and greatest with respect to TFMs
- Codebelt.Extensions.Xunit.Hosti...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
[style] ~20-~20: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ....Hosting updated to latest and greatest with respect to TFMs
- Codebelt.Extensions.Xunit.Hosti...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
[style] ~21-~21: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...pNetCore updated to latest and greatest with respect to TFMs
Changed
- HostFixture cl...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
⏰ Context from checks skipped due to timeout of 90000ms (6)
- GitHub Check: 🧪 Test (windows-2022, Release)
- GitHub Check: 🧪 Test (windows-2022, Debug)
- GitHub Check: 🧪 Test (ubuntu-22.04, Release)
- GitHub Check: 📦 Pack (Release)
- GitHub Check: 🧪 Test (ubuntu-22.04, Debug)
- GitHub Check: 📦 Pack (Debug)
🔇 Additional comments (2)
CHANGELOG.md (2)
10-13: LGTM! Clear version header and introduction.The version header follows the Keep a Changelog format, and the introduction clearly states the purpose of this service update.
17-22: Document all significant changes from the PR.The changelog is missing several changes mentioned in the PR objectives:
- nginx version update in .docfx/Dockerfile.docfx
- TargetFramework update to net9.0
- Push trigger removal from pipelines.yml
- Package version updates (Microsoft.Bcl.AsyncInterfaces, Microsoft.NET.Test.Sdk, xunit)
Consider adding these changes under appropriate sections (Dependencies, Changed, etc.) for completeness.
🧰 Tools
🪛 LanguageTool
[style] ~19-~19: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...ns.Xunit updated to latest and greatest with respect to TFMs
- Codebelt.Extensions.Xunit.Hosti...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
[style] ~20-~20: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ....Hosting updated to latest and greatest with respect to TFMs
- Codebelt.Extensions.Xunit.Hosti...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
[style] ~21-~21: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...pNetCore updated to latest and greatest with respect to TFMsChanged
- HostFixture cl...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
|
This pull request includes several updates across multiple files to improve compatibility with .NET 9 and update package dependencies. The most important changes include updating Docker and build configurations, modifying package dependencies, and removing obsolete code for better compatibility.
Configuration Updates:
nginxversion in.docfx/Dockerfile.docfxto1.27.3-alpine.TargetFrameworktonet9.0and modified footer copyright in.docfx/docfx.json. [1] [2]pushtrigger configuration in.github/workflows/pipelines.yml.Dependency Updates:
Microsoft.Bcl.AsyncInterfaces,Microsoft.NET.Test.Sdk, andxunitinDirectory.Packages.props.testenvironments.json.Code and Documentation Updates:
IHostingEnvironmentcode and updated related classes and interfaces insrc/Codebelt.Extensions.Xunit.Hosting. [1] [2] [3] [4] [5] [6] [7] [8]9.0.1inCHANGELOG.mdand updatedPackageReleaseNotes.txtfiles. [1] [2] [3] [4]License Update:
LICENSEto include 2025.These changes ensure the project stays up-to-date with the latest .NET framework and dependencies, while also cleaning up deprecated code.
Summary by CodeRabbit
Release Notes v9.0.1
New Features
FakeHttpContextAccessorsupport forIServiceProvidersFeaturePackage Updates
IHostingEnvironmentInfrastructure
Improvements
AddFakeHttpContextAccessormethod