Description
according to https://github.com/dotnet/maintenance-packages/blob/main/package-support-policy.md
"The library packages have the same support model as the .NET versions that they target."
Can i confirm that either 1.0.2 is still a supported version, or could older versions that target unsupported .net packages (and as such are possibly unsupported) please be marked as deprecated (on nuget, deprecated : reason "targets unsupported .net" but still listed)?
Azure/azure-webjobs-sdk#3161 has a core azure library not shifting dependencies relying on v1.0.2 is "still supported in nuget"
this has caused
https://learn.microsoft.com/en-us/answers/questions/2286258/azure-core-could-not-load-file-or-assembly-system
and presumably other grief where a library loads the incorrect dependency.
non-deprecated packages that target deprecated dependences can cause problems.
Reproduction Steps
nuget add System.Memory.Data 1.0.2- see a 5.5 year old package that pulls in legacy json packages and others - and no warnings.
Expected behavior
usage of super old packages is discouraged
Actual behavior
people are raising tickets in various because they accidently pulled in very old libraries and their old dependencies
Regression?
No response
Known Workarounds
No response
Configuration
No response
Other information
No response
Description
according to https://github.com/dotnet/maintenance-packages/blob/main/package-support-policy.md
"The library packages have the same support model as the .NET versions that they target."
Can i confirm that either 1.0.2 is still a supported version, or could older versions that target unsupported .net packages (and as such are possibly unsupported) please be marked as deprecated (on nuget, deprecated : reason "targets unsupported .net" but still listed)?
Azure/azure-webjobs-sdk#3161 has a core azure library not shifting dependencies relying on v1.0.2 is "still supported in nuget"
this has caused
https://learn.microsoft.com/en-us/answers/questions/2286258/azure-core-could-not-load-file-or-assembly-system
and presumably other grief where a library loads the incorrect dependency.
non-deprecated packages that target deprecated dependences can cause problems.
Reproduction Steps
nuget add System.Memory.Data 1.0.2- see a 5.5 year old package that pulls in legacy json packages and others - and no warnings.
Expected behavior
usage of super old packages is discouraged
Actual behavior
people are raising tickets in various because they accidently pulled in very old libraries and their old dependencies
Regression?
No response
Known Workarounds
No response
Configuration
No response
Other information
No response