Skip to content
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

Update dependencies and workaround dotnet/sdk#2976 #238

Merged
merged 4 commits into from
Feb 22, 2019

Conversation

natemcmaster
Copy link
Contributor

@natemcmaster natemcmaster commented Feb 22, 2019

@natemcmaster natemcmaster requested a review from dougbu February 22, 2019 04:58
@natemcmaster
Copy link
Contributor Author

Ready to merge, just waiting for review approval.

Copy link
Member

@dougbu dougbu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we move aspnet/Extensions to Xunit 2.4.1 and (then) the other repos?

@@ -128,8 +128,7 @@
<VSIX_MicrosoftVisualStudioLanguageServicesPackageVersion>3.0.0-beta2-18612-05</VSIX_MicrosoftVisualStudioLanguageServicesPackageVersion>
<VSIX_MicrosoftVisualStudioLanguageServicesRazorRemoteClientPackageVersion>3.0.0-beta2-18612-05</VSIX_MicrosoftVisualStudioLanguageServicesRazorRemoteClientPackageVersion>
<XunitAnalyzersPackageVersion>0.10.0</XunitAnalyzersPackageVersion>
<XunitPackageVersion>2.3.1</XunitPackageVersion>
<XunitRunnerVisualStudioPackageVersion>2.4.0</XunitRunnerVisualStudioPackageVersion>
<XunitVersion>2.4.1</XunitVersion>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Odd. aspnet/Extensions is on 2.4.0 and that bumping things up here would cause different package downgrade errors. Glad it doesn't.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we move aspnet/Extensions to Xunit 2.4.1 and (then) the other repos?

Yes, but I would do it in reverse order. Move AspNetCore to 2.4.1, then Extensions

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Move AspNetCore to 2.4.1, then Extensions

In release/3.0-preview3 or master?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

master. It's not urgent for preview3

@natemcmaster natemcmaster merged commit 6708297 into release/3.0-preview3 Feb 22, 2019
@natemcmaster natemcmaster deleted the namc/update branch February 22, 2019 18:24
JunTaoLuo pushed a commit to dotnet/aspnetcore that referenced this pull request May 17, 2020
…dotnet/razor#238)

* Update dependencies
* Add workaround for dotnet/sdkdotnet/aspnetcore-tooling#2976
* Remove unused NETStandard package version variable and overrides
* Update xunit to 2.4.1
\n\nCommit migrated from dotnet/razor@6708297
dougbu pushed a commit to dougbu/razor-compiler that referenced this pull request Nov 17, 2021
…dotnet/razor#238)

* Update dependencies
* Add workaround for dotnet/sdkdotnet/aspnetcore-tooling#2976
* Remove unused NETStandard package version variable and overrides
* Update xunit to 2.4.1
\n\nCommit migrated from dotnet/razor@6708297

Commit migrated from dotnet/aspnetcore@61e85256a653
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants