feat: loosen package versions for .NET6/.NET8#1008
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
This PR adjusts central package version management and Renovate automation to better align dependency versions with the intended target frameworks, while also tightening test warning visibility.
Changes:
- Updated
Directory.Packages.propsto applySystem.Threading.Channels,System.Linq.Async, andMicrosoft.Bcl.Memoryversions conditionally per TFM (including explicit handling for netstandard and net9). - Added Renovate rules to freeze legacy version “lines” for
System.Threading.ChannelsandSystem.Linq.Asyncwhile allowing newer TFM entries to keep updating. - Removed
NU1608from test projects’ suppressed warnings so version-constraint issues are surfaced.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| Tests/Directory.Build.props | Stops suppressing NU1608 in tests to surface dependency-constraint issues. |
| renovate.json | Adds packageRules to freeze specific legacy dependency version lines per package. |
| Directory.Packages.props | Refines per-TFM central versions and loosens exact pins for select packages. |
|
|
This is addressed in release v6.3.0. |
This was referenced May 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



This pull request updates package management and configuration for multiple target frameworks, improves dependency alignment, and adjusts warning suppression for test projects. The most important changes are grouped below.
Package versioning and target framework alignment
System.Threading.ChannelsandSystem.Linq.Asyncpackage references inDirectory.Packages.propsto better align versions with the appropriate target frameworks, including explicit handling fornetstandard2.0,netstandard2.1,net8.0, andnet9.0. This ensures that each framework uses the most compatible and runtime-aligned package version.Microsoft.Bcl.Memoryfor specific target frameworks (net8.0,net9.0,netstandard2.1,netstandard2.0), improving dependency management and avoiding unnecessary package references for other frameworks.Dependency update automation
renovate.jsonto freeze updates for legacySystem.Threading.ChannelsandSystem.Linq.Asyncpackage versions for certain target frameworks, ensuring these stay aligned with runtime-bundled assemblies and only newer TFM entries are auto-updated.Build and test configuration
Tests/Directory.Build.propsby removingNU1608from theNoWarnlist, allowing these warnings to be surfaced and addressed.