{{ message }}
Repository navigation
Running dotnet outdated detects available update for a global package but running --upgrade doesn't update it #681
Description
My repo is onboarded to CPM, e.g. has the following file:
- Directory.Packages.props
Which then has the following entry:
<ItemGroup Condition="'$(MSBuildProjectExtension)' == '.csproj'">
<GlobalPackageReference Include="Meziantou.Analyzer" Version="2.0.222">
<PrivateAssets>all</PrivateAssets>
<IncludeAssets>runtime; build; native; contentfiles; analyzers</IncludeAssets>
</GlobalPackageReference>
</ItemGroup >The current version is 2.0.222 and the latest available is 2.0.224.
Running dotnet outdated detects available update:
» MyProject
[net9.0]
Meziantou.Analyzer 2.0.222 -> 2.0.224
However, running & dotnet outdated --upgrade leaves it as-is.
Activity
abatishchev commentedon Nov 17, 2025
hi @slang25, is this project maintained? I see many issues are never responded to.
slang25 commentedon Nov 17, 2025
Yes, although I have a long list of things I look after and this is no where near the top, so I will get to some of these issues and PRs
abatishchev commentedon Nov 17, 2025
Awesome, thanks! I realize all the difficulties of maintaining a (popular) OSS project. If a code change is needed to fix this issue, please let me know - I'd love to do my part and contribute.
wallymathieu commentedon Dec 3, 2025
This looks fixed?
abatishchev commentedon Dec 3, 2025
Nope, still doesn't work for me, even in version
4.6.9+5bbcc6b6fafbeaa45b590722067e334506afdb48:(wallymathieu commentedon Dec 3, 2025
Yes, I got confused, because previously it told that it failed while trying to update, while now it just does not update.
k-cup-vm commentedon Feb 18, 2026
Issue still present in 4.7.0, looks like #697 didn't fix it. Changing the package from
GlobalPackageReferenceto regularPackageVersion/PackageReferencemakes the package update successfully.