Odd `aspire update` behaviour.

[afscrome]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

I'm getting some strange behaviour with aspire update. - the default channel is giving me pre-release builds, whilst the stable channel can't find any builds.

Note, I am running with the config recommended by @joperezr's instructions at https://discord.com/channels/1361488941836140614/1420279564952666122/1473756392367325185 .

Expected Behavior

1. aspire update --channel default should only show stable packages unless I've done something to opt into pre-release packages.
2. aspire update --channel stable should list packages

Steps To Reproduce

Not entirely sure of exact repo steps right now - I'll do some more testing tonight on my personal machine to see if I can narrow it down some more

I suspect this is a side effect of my company's internal nuget package setup

• all nuget packages have to be pulled through our internal proxy
• nuget.org is blocked at an infrastructure level to ensure packages are pulled through our proxy
• The dnceng feeds are set as upstreams in our proxy to allow pre-release aspire packages to be pulled through our proxy

Nuget.config files:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
    <packageSources>
        <clear />
        <add key="REDACTED" value="REDACTED" />
    </packageSources>
    <packageSourceMapping>
        <clear />
        <packageSource key="REDACTED">
            <package pattern="*" />
        </packageSource>
    </packageSourceMapping>
</configuration>

Exceptions (if any)

No response

.NET Version info

> aspire --version
13.2.0-pr.14585.gb038ca04

Anything else?

I haven't used aspire update much prior to 13.2, so can't confirm if this is a new issue or not - I'll try and do some more testing later to confirm.