Open Closed

Nuget Packages not updating to 10.5 #10768


User avatar
0
florian.neuhaus created

ABP.IO 10.5 has been released final. if I do an abp update, I still receive the nuget packages from 10.4.1.

  • ABP Studio is up to date
  • CLI is up to date
  • Nuget cache has been cleared (dotnet nuget locals all --clear)

abp update [13:12:02 INF] Volo packages are updated in fullbench-dll solution [13:12:02 INF] Package: "Volo.Abp.AspNetCore.Mvc-v10.4.1" is up to date [13:12:02 INF] Package: "Volo.Abp.PermissionManagement.Application.Contracts-v10.4.1" is up to date [13:12:02 INF] Package: "Volo.Abp.BackgroundJobs.Domain.Shared-v10.4.1" is up to date [13:12:02 INF] Package: "Volo.Abp.AspNetCore.Mvc-v10.4.1" is up to date [13:12:02 INF] Package: "Volo.Abp.AspNetCore.Mvc-v10.4.1" is up to date [13:12:02 INF] Package: "Volo.Abp.EntityFrameworkCore.SqlServer-v10.4.1" is up to date ... more logs

Markdown supported.
Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

4 Answer(s)
  • User Avatar
    0
    AI-Bot created
    Support Team ABP Agent
    • abp update only updates to the latest ABP packages it can see from your configured NuGet feeds. When it says "Volo.Abp.*-v10.4.1 is up to date", it typically means your machine is not able to resolve 10.5.x from any enabled package source, so 10.4.1 is the highest version available from the sources it is using.

    • Fix steps (in order), to force NuGet/CLI to actually see 10.5:

      1. Check which sources NuGet is using:
    dotnet nuget list source
    
     Ensure `nuget.org` is enabled and reachable.
    
    1. Verify NuGet can resolve 10.5 from your sources (this is the real test):
    dotnet list <AnyProject>.csproj package --include-transitive | findstr Volo.Abp
    
     Then try:
    
    dotnet add <AnyProject>.csproj package Volo.Abp.AspNetCore.Mvc --version 10.5.0
    
     If this fails, it’s a NuGet-source/config/network issue (not ABP update).
    
    1. Inspect global/user NuGet.config for a corporate feed, source mapping, or a config that blocks nuget.org:

      • Typical locations: %AppData%\NuGet\NuGet.Config (Windows) / ~/.nuget/NuGet/NuGet.Config (Linux/macOS)
      • Common culprits:
        • packageSourceMapping that does not map Volo.* / Volo.Abp.* to nuget.org
        • A custom feed set as the only source, or nuget.org disabled
        • A failing feed that breaks restore/version queries in your environment
    2. After fixing sources, run:

    dotnet nuget locals all --clear
         abp update
    
     Now it should move to 10.5.x.
    
    1. If you’re on the Commercial version and use a private/proxy NuGet feed, ensure that feed is synced and actually contains 10.5.x. If the proxy feed only has 10.4.1, ABP can’t upgrade beyond that until the feed has the packages.

    Sources:

    • https://abp.io/docs/latest/CLI#update
    • https://abp.io/community/articles/2u589bsc
    • https://abp.io/docs/10.5/release-info/migration-guides/abp-10-5

    This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.

    Markdown supported.
    Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)
  • User Avatar
    0
    maliming created
    Support Team Fullstack Developer

    Hi,

    This isn't a NuGet source / feed / cache issue on your side. When you run abp update without a version, the CLI decides the "latest stable" from a version list we publish, not from NuGet directly. That list hadn't been bumped to 10.5 yet, so the CLI still saw 10.4.1 as the newest and reported everything as up to date. The 10.5 packages themselves are already on NuGet.

    We're updating that list now. Give it a little while, then run abp update again and it'll pick up 10.5.

    If you'd rather update right away without waiting, pin the version explicitly:

    abp update -v 10.5.0 -lv 5.5.0
    

    The -lv 5.5.0 part is needed so the LeptonX packages get updated too (10.5 ships with LeptonX 5.5.0).

    Thanks

    Markdown supported.
    Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)
  • User Avatar
    0
    florian.neuhaus created

    Hi @maliming Thanks for clarifying the release process. So then we were a little too fast. Probably you should mention this in your release blog-post. Thanks, Florian

    Markdown supported.
    Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)
  • User Avatar
    0
    maliming created
    Support Team Fullstack Developer

    : )

    Markdown supported.
    Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)
Boost Your Development
ABP Live Training
Packages
See Trainings
Mastering ABP Framework Book
The Official Guide
Mastering
ABP Framework
Learn More
Mastering ABP Framework Book
Made with ❤️ on ABP v10.8.0-preview. Updated on September 16, 2026, 14:50
1
ABP Assistant
🔐 You need to be logged in to use the chatbot. Please log in first.