Figure out a way to deal with new CoreCLR packages

Question

Figure out a way to deal with new CoreCLR packages

ajaybhargavb opened this issue 8 years ago · comments

After a new successful build of CoreCLR, our Coherence check fails with errors like Microsoft.Extensions.DependencyInjection.1.2.0-preview1-22941 depends on NETStandard.Library v[1.6.1, ) (.NETStandard,Version=v1.1) when the latest build is v1.6.2-beta-24816-02.
I've temporarily disabled product packages verification.

cc' @Eilon @pranavkm

Eilon Lipton · Answer 1 · Wed Dec 21 2016 02:23:48 GMT+0800 (China Standard Time)

Parking this on your plate until we can sync with @pranavkm .

Pranav K · Answer 2 · Fri Dec 23 2016 02:40:45 GMT+0800 (China Standard Time)

Should be fixed now. I checked in changes to all the repos to start referencing the new CoreFx packages and turned the coherence check back on. We can close this once we have a Coherence build.

Eilon Lipton · Answer 3 · Fri Dec 23 2016 06:03:36 GMT+0800 (China Standard Time)

How can we make this be more automatic?

Murat Girgin · Answer 4 · Thu Mar 30 2017 02:04:00 GMT+0800 (China Standard Time)

@pranavkm Good to close?

Eilon Lipton · Answer 5 · Sat Apr 08 2017 04:15:45 GMT+0800 (China Standard Time)

Doesn't appear to be any work left here. If this becomes a problem in the future we'll investigate.