-
Notifications
You must be signed in to change notification settings - Fork 676
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump razor #7005
Bump razor #7005
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would you mind updating the changelog as well with the fixes in this insertion?
I did it manually by diffing builds, but is there a tool we have for this? |
In the razor repo, you can run Then I usually filter out everything that isn't relevant for vscode / adjust titles to better explain the changes. |
I knew about the |
CHANGELOG.md
Outdated
* Fix hot path string allocations from ProjectKey (PR: [#10138](https://github.com/dotnet/razor/pull/10138)) | ||
* Disable latest runtime patch (PR: [#10133](https://github.com/dotnet/razor/pull/10133)) | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nits: Two blank lines (though I doubt markdown cares) and BackgroundDocumentGenerator is not used in VS Code (though I doubt anyone reading the notes cares.. or indeed reads the notes 😛)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the comments and thank you @ryzngard for helping out |
Release from build https://dev.azure.com/dnceng/internal/_build/results?buildId=2414428&view=results