This repository has been archived by the owner on Dec 21, 2021. It is now read-only.
Fix installation of .NET versions where format of latest release date differs from the actual release date. #13
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
…date. For .NET 5.0.4 the date format of the latest-release-date field differed from the release-date field. This is a backup to make the task a little more robust.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The
latest-releaseandlatest-release-dateare used to select the latest release. This will return$nullif the date format of thelatest-release-dateis wrong. If we get$nullwe try to select the latest release by only filtering on the version and not the date.This fixes issue: #12