Fix stable publishing issue#3711
Merged
mmitche merged 1 commit intodotnet:release/10.0.1xxfrom Dec 5, 2025
Merged
Conversation
When dotnet#3668 went it, it removed DotNetFinalVersionKind from being set at the root level of the VMR. This unintentionally was causing the VMR publishing process to mark all shipping assets as CouldBeStable=true when DotNetFinalVersionKind=release, rather than using the values that were coming from the repos. The fix here is to not set PublishingVersion at the repo level. This will cause VMR builds to use V4 publishing for the repo builds, which will set CouldBeStable appropriately. Only winforms and wpf were manually setting this.
Member
Author
|
Resolves #3706 |
rbhanda
approved these changes
Dec 5, 2025
hoyosjs
approved these changes
Dec 5, 2025
thalinda-oss
approved these changes
Dec 6, 2025
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
4 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.
When #3668 went it, it removed DotNetFinalVersionKind from being set at the root level of the VMR. This unintentionally was causing the VMR publishing process to mark all shipping assets as CouldBeStable=true when DotNetFinalVersionKind=release, rather than using the values that were coming from the repos. The fix here is to not set PublishingVersion at the repo level. This will cause VMR builds to use V4 publishing for the repo builds, which will set CouldBeStable appropriately. Only winforms and wpf were manually setting this.