2.0.0 Release #38
Merged
2.0.0 Release #38
+428
−505
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
Mapping LogLevel.None to LogEventLevel.Fatal.
Update for ASP.NET Core 2.0
Less likely to change as we work to accommodate 2.0 APIs
Add a configuration option to specify the output template
fixing repository url
Bumps [Microsoft.AspNetCore.All](https://github.com/aspnet/Universe) from 2.0.0 to 2.0.9. - [Release notes](https://github.com/aspnet/Universe/releases) - [Changelog](https://github.com/aspnet/Universe/blob/master/docs/CrossRepoBreakingChanges.md) - [Commits](aspnet/Universe@2.0.0...2.0.9) Signed-off-by: dependabot[bot] <[email protected]>
…cation/Microsoft.AspNetCore.All-2.0.9 Bump Microsoft.AspNetCore.All from 2.0.0 to 2.0.9 in /example/WebApplication
Corrected spelling mistake
Update README.md
|
🎉 Thanks @nblumhardt 😄 |
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.
This is a very late release, since we've fallen behind on maintaining this package. Pushing out the 2.0 changes in their current state should unblock things and let forward progress again be made.
LogLevel.NonetoLogEventLevel.Fatal(@kellystuard)Closes #32, #37.