Add 2.0.0 to AppVeyor builds #1530
Merged
Conversation
This file contains 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
rjmholt
requested review from
TylerLeonhardt,
rkeithhill and
SeeminglyScience
|
I'm confused by this PR... are we going to have a 2.0.0 branch in vscode-powershell as well? |
|
Well, I'm mainly doing it so the client can have a 2.0 version number. But maybe we don't want that? |
|
Definitely need a 2.0 client version since we're dropping older PowerShell versions. Even if it is more or less a dependency change. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds the 2.0.0 branch to the AppVeyor build list so we can get a 2.0.0 release artefact.
Not sure what
developwas, but I'm pretty sure we're not using it any more.