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

package downgrade caused by v2.17.8 #980

Closed
baywet opened this issue Nov 15, 2023 · 7 comments
Closed

package downgrade caused by v2.17.8 #980

baywet opened this issue Nov 15, 2023 · 7 comments
Assignees
Labels

Comments

@baywet
Copy link
Member

baywet commented Nov 15, 2023

Hi everyone,
Upgrading to 2.17.8 causes package downgrade warnings.
See this example.

I believe merging #967 and #965 should fix this.

@AArnott
Copy link
Member

AArnott commented Nov 15, 2023

Whoa. I didn't think we'd be possible of introducing package downgrade warnings at this level, but it appears you're right. Thanks for reporting.

@AArnott AArnott self-assigned this Nov 15, 2023
@AArnott AArnott added the bug label Nov 15, 2023
@AArnott
Copy link
Member

AArnott commented Nov 15, 2023

In the meantime, you can always workaround it by adding a PackageReference to the newer versioned package directly to your project file.

@baywet
Copy link
Member Author

baywet commented Nov 15, 2023

in our case we're not in a rush to get the newer version, we'll just wait for the next one. I was simply reporting this so the problem gets addressed.

@AArnott
Copy link
Member

AArnott commented Nov 15, 2023

I think this is the crux of the issue, actually. It comes from your build log:

error NU1603: Warning As Error: StreamJsonRpc 2.17.8 depends on Microsoft.VisualStudio.Threading (>= 17.7.35) but Microsoft.VisualStudio.Threading 17.7.35 was not found. An approximate best match of Microsoft.VisualStudio.Threading 17.8.14 was resolved.

It seems a version of Microsoft.VisualStudio.Threading is missing from nuget.org. Pushing that version will probably fix your build.

@AArnott
Copy link
Member

AArnott commented Nov 15, 2023

Apparently we tried to push that missing package yesterday, but nuget.org rejected it. We're pursuing mitigations.

@AArnott
Copy link
Member

AArnott commented Nov 17, 2023

This should be resolved. Can you please confirm, @baywet?

@baywet
Copy link
Member Author

baywet commented Nov 17, 2023

Yes it now works. Thanks for the help. Closing.

@baywet baywet closed this as completed Nov 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants