Repository navigation
.NET SDK and package updates - #67
Merged
Merged
Conversation
Member
Author
|
Looks like something's wrong with our Appveyor integration; I'll reinitialize it. |
Member
Author
|
I believe the problem with CI was because I recently cleaned up our organization integration list; hope it's fixed now. Note that Appveyor build is actually okay; it just cannot report the status here. |
Member
Author
|
Thanks for the review. |
Member
Author
|
I had to do some maintainership commits to fix the build afterwards, but that's okay. |
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
2 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.
Hereby I update .NET Core SDK to the latest stable version, and also update package versions to follow the recent security bulletins. The main visible change is that we migrate from (now obsolete)
project.jsonto (restored in its rights)*.fsproj.Also I've updated the
npm-shrinkwrapconfiguration to match the latest npm 5 recommendations (and it should be backwards-compatible).That will likely require us to update .NET Core version on our production site for the good (we're targeting
netcoreapp1.1now, that means we'll need .NET Core 1.1 installed).Closes #65.