Removes faulty explicit version ordering #1095
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
|
@twangboy Can you review this PR when you have a moment? |
|
@twangboy Bump for a review here. :) |
twangboy
approved these changes
Jun 20, 2017
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.
What does this PR do?
Changes the version ordering to rely on the correct ordering already present in the repo, and selects the last (Most recent) version. This removes the explicit ordering done with
Select-Object -Descendingas this works alphabetically and does not correctly order versions (eg..11comes before.2).What issues does this PR fix or reference?
#1094
Previous Behavior
Not passing
-versionwould fetch the wrong version, where it should fetch the latest.New Behavior
Now correctly fetches latest version.