Fix handling of NuGet package version in VSIX #1536
Merged
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
vineeththomasalex
previously approved these changes
Feb 7, 2026
manodasanW
approved these changes
Feb 10, 2026
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.
We recently add a prerelease tag to the NuGet package generated from unofficial builds, but this prerelease tag was mistakenly getting picked up by the VSIX version, and VSIX doesn't support prerelease.
This change cleans this up and adds a separate property/variable for the VSIX, so we can treat the NuGet and VSIX versions separately.
Tested the PR ADO pipeline with this change and got a successful build: https://dev.azure.com/microsoft/Dart/_build/results?buildId=139282480&view=results