[release/11.0] Mark ILVerify and ILVerification as shipping - #134816
Merged
Merged
Conversation
Also implement required changes to make our package validation tooling happy. Fixes #134763
|
Azure Pipelines: Successfully started running 4 pipeline(s). 12 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
github-actions
Bot
added
the
area-Tools-ILVerification
Contributor
|
Tagging subscribers to this area: @JulieLeeMSFT, @dotnet/jit-contrib |
jkotas
approved these changes
Sep 28, 2026
JulieLeeMSFT
added
the
Servicing-consider
JulieLeeMSFT
added
Servicing-approved
Member
|
@jkoritzinsky, please check test failures. |
github-actions
Bot
added
the
area-Tools-ILVerification
Contributor
|
Tagging subscribers to this area: @JulieLeeMSFT, @dotnet/jit-contrib |
Member
|
/ba-g known test failures are unrelated (they all seem to have KBEs too). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backport of #134804 to release/11.0
/cc @jkoritzinsky
Customer Impact
dotnet-ilverify and Microsoft.DotNet.ILVerification nuget packages are not published on nuget.org
Regression
#120853
Testing
Validated that the package files get put into the Shipping directory in the artifacts.
Risk
Low, only adjusts metadata in the project and text-only markdown files.
IMPORTANT: If this backport is for a servicing release, please verify that:
release/X.0-staging, notrelease/X.0.release/X.0(no-stagingsuffix).Package authoring no longer needed in .NET 9
IMPORTANT: Starting with .NET 9, you no longer need to edit a NuGet package's csproj to enable building and bump the version.
Keep in mind that we still need package authoring in .NET 8 and older versions.