-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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 versions again #5
Conversation
Let's get everything working before merging ... |
Update global.json to match |
OK works for me on Windows and Linux. I had to use a lot of asterisks in the nuget.config just to get us through to .NET 8 GA -- there are so many packages of various versions in various different feeds it really isn't worth trying to lock down here which come from where. I gave up. It should be simple at .NET 8 GA |
Looks like @captainsafia changed Aspire to preview.2 -- I assume this was temporary to get the Mac temp path fix until we figure out why preview.1 aspire bits are no longer being pushed to the feeds. |
Correct! I suppose we'll want to target preview.1 in this repo once Aspire goes live. |
if this works for you too @captainsafia shall we merge? |
It works for me too @danmoseley. Thanks! |
We should be downgrading the aspire version to preview1. |
Right, see my comment above, we need the mac fix. @captainsafia did you resolve the issue of not getting the updated preview 1 bit ons the feed? |
@joperezr 8.0.0-preview.1.23530.4 is still the latest Aspire.Hosting preview1 on https://pkgs.dev.azure.com/dnceng/internal/_packaging/dotnet-tools-internal/nuget/v3/index.json. This is blocking eshop picking up the .net conf Aspire. |
OK we found the aspire preview 1 bits are now in yet another feed. Added that and moved back to preview 1. Should be good to go now. |
@adityamandaleeka do you want to sign off / merge? |
Sorry for the confusion. Builds were being produced but not pushed to the feed because we were adding new channels that were specific to Aspire so that repos (like eshop) can take dependencies using dependency flow. We just merged this change dotnet/arcade#14184 (review) into arcade which adds support for those new channels and once that is ingested it will make it so builds resume getting pushed. For now, Let me know if you need a new build pushed to a feed and I can manually promote it |
this time past the stable versioning of runtime parts.