Test for outdated packages suggests the wrong version as the latest
- Dominant language
- C#
- Stars
- 3.2k
- Forks
- 1.3k
- PR merge metrics
- PR metrics pending
Description
### Describe the bug
I have a .NET 10 project that references version 2026.7.1 of the QuestPDF package.
When I check for outdated packages it reports 2202.8.2 as the latest instead of 2026.7.2.
### Steps to reproduce
Create a project that references version 2026.7.1 of the QuestPDF package.
Run `dotnet list package --outdated`
Output:
```
Project `{project-name-here}` has the following updates to its packages
[net10.0]:
Top-level Package Requested Resolved Latest
> QuestPDF 2026.7.1 2026.7.1 2202.8.2
```
### Expected behavior
Show actual latest available package version that has not been unlisted. So, 2026.7.2 at the time of this writing.
### Actual behavior
Shows the highest version that was inadvertently released due to a typo. The version has been unlisted according to the project maintainers. See [QuestPDF #1450](https://github.com/QuestPDF/QuestPDF/issues/1450)
Note that nuget.exe does not list that version when you run `nuget.exe search QuestPDF`
### Is this a regression?
_No response_
### Are there any workarounds?
Periodically look for the package at `nuget.org` to see if there is a newer version.
PR code reviews to make sure none of the devs try to upgrade to the very old version.
Not a deal breaker, just an annoyance.
### dotnet --info output
```console
.NET SDK:
Version: 10.0.302
Commit: 35b593bebf
Workload version: 10.0.300-manifests.714b12c0
MSBuild version: 18.6.11+35b593beb
Runtime Environment:
OS Name: Windows
OS Version: 10.0.22631
OS Platform: Windows
RID: win-x64
Base Path: C:\Program Files\dotnet\sdk\10.0.302\
.NET workloads installed:
There are no installed workloads to display.
Configured to use workload sets when installing new manifests.
No workload sets are installed. Run "dotnet workload restore" to install a workload set.
Host:
Version: 10.0.10
Architecture: x64
Commit: f7d90799ce
.NET SDKs installed:
8.0.423 [C:\Program Files\dotnet\sdk]
10.0.302 [C:\Program Files\dotnet\sdk]
.NET runtimes installed:
Microsoft.AspNetCore.App 8.0.29 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 10.0.10 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 8.0.29 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 10.0.10 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 8.0.29 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 10.0.10 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Other architectures found:
x86 [C:\Program Files (x86)\dotnet]
registered at [HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x86\InstallLocation]
Environment variables:
DOTNET_CLI_TELEMETRY_OPTOUT [1]
global.json file:
Not found
Learn more:
https://aka.ms/dotnet/info
Download .NET:
https://aka.ms/dotnet/download
```
### IDE version
_No response_
### Other details
_No response_
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing `dotnet list package --outdated` with the QuestPDF versions shown in the report, then trace the package-version resolution used by this command. Done means unlisted versions are excluded and the command reports the actual latest available version, such as 2026.7.2 instead of 2202.8.2.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100