Skip to content

CI Update - Add additional package-provider monikers for .NET Framework (chunked) #11522

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 12 commits into from
Jun 30, 2025

Conversation

gewarren
Copy link
Contributor

@gewarren gewarren commented Jun 27, 2025

(View by commit.)

Preview of FrozenSet<T> for .NET Framework 4.8.1 (package-provided) moniker.

Fixes #11523
Replaces #11510.

Build.Reason:Manual by Genevieve Warren
Build.Url:https://apidrop.visualstudio.com/Content%20CI/_build/results?buildId=544797&view=results
source_repo.branch:packages-netfx-expansion
source_repo.url:https://apidrop.visualstudio.com/_git/binaries

Summary

If a NuGet package targets .NET Framework 4.6.2 (for example), the docs only show the APIs in the package as applying to .NET Framework 4.6.2, even though they technically apply to all the later .NET Framework versions as well. This PR expands the "applies to" data for APIs from packages that target .NET Framework.

PackageIndexer changes are here.

Copy link
Member

@BillWagner BillWagner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This LGTM @gewarren

Let's :shipit:

@gewarren gewarren merged commit 28e189e into dotnet:main Jun 30, 2025
5 checks passed
@gewarren gewarren deleted the packages-netfx-expansion-chunked branch June 30, 2025 14:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Expand to all .NET Framework monikers for package-provided APIs
2 participants