Components.AI net11 package depends on unavailable .NET 12 package
- Dominant language
- C#
- Stars
- 38.4k
- Forks
- 10.9k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 276
Description
### Is there an existing issue for this?
- [x] I have searched the existing issues
### Describe the bug
`Microsoft.AspNetCore.Components.AI` version `0.1.0-preview.1.26459.102` is published to NuGet.org, but its `net11.0` dependency group references:
```xml
```
`Microsoft.AspNetCore.Components.Web` version `12.0.0-alpha.1.26459.102` is not available on NuGet.org. As a result, consumers cannot restore the Components AI package using only NuGet.org and must either add a .NET shipping feed or force a package downgrade.
This surfaced while preparing danroth27/AgenticUI#5 as a clone-and-run sample for an upcoming .NET Blog post. The application targets `net11.0` and builds successfully when the dependency is explicitly pinned to `Microsoft.AspNetCore.Components.Web` `11.0.0-rc.1.26425.128`, but that requires suppressing `NU1605` and `NU1510`, which is not appropriate guidance for a best-practices sample.
Package metadata identifies source commit `4ec325806886c5d729b5abc3515c4a4052f313e9` in `dotnet/dotnet`.
@kotlarmilos, could you please take a look since you worked on the Components AI package versioning and release cadence?
### Expected behavior
The `net11.0` Components AI package should depend on a compatible .NET 11 `Microsoft.AspNetCore.Components.Web` version available from NuGet.org, allowing restore without custom feeds or dependency-downgrade suppressions.
### Steps to reproduce
1. Configure NuGet.org as the only package source and use an empty global packages folder.
2. Create or use a `net11.0` ASP.NET Core project.
3. Add:
```xml
```
4. Run `dotnet restore`.
Restore attempts to resolve `Microsoft.AspNetCore.Components.Web` `12.0.0-alpha.1.26459.102`, which is unavailable from NuGet.org.
### .NET version
`11.0.100-rc.1.26425.128`
### Anything else?
The package itself and its other dependency, `Microsoft.Extensions.AI.Abstractions` `10.6.0`, are available from NuGet.org. The problematic dependency is visible directly in the published package's `.nuspec`.
Contributor guide
Assessment
This issue has not been assessed yet.