Allow Roslyn to create stable packages in VMR #2449
Draft
Conversation
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
This was referenced Sep 16, 2025
jjonescz
approved these changes
Sep 19, 2025
Member
There was a problem hiding this comment.
Planning on taking this for rc2.
You should target release/10.0.1xx I think
Member
There was a problem hiding this comment.
yes but just FYI we don't have any automated merges from release/10.0.1xx -> main so you need to /backport it to the other branch regardless
JoeRobich
approved these changes
Sep 19, 2025
mmitche
approved these changes
Sep 19, 2025
Member
Author
|
Waiting to take this until we know how future versions of VS will align with the SDK (not taking this for rc2). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 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.
Paired with dotnet/roslyn#80009
We will be manually publishing Roslyn packages created by the VMR on SDK releases (instead of our official build), hence need to opt-in to stable package creation. Planning on taking this for rc2.
Validation prerelease - https://dev.azure.com/dnceng/internal/_build/results?buildId=2794951&view=results
Validation release - https://dev.azure.com/dnceng/internal/_build/results?buildId=2794953&view=results