Brett V. Forsgren

There's a slightly odd workaround that we found; it requires using an HTML cell for the `import` line (and assigning it to the `window` object) and in a separate JS...

For the maintainers on this repo: Several years ago I worked on the F# compiler and language service, so I have a passing understanding of Paket and its importance to...

As I understand it, this will only work for Azure DevOps package feeds, but not private feeds from other providers (e.g., GitHub, AWS, Artifactory, MyGet, etc.) so the NuGet.Config mangling...

@trejjam I only recently learned about how credentials are used in the update process and my understanding is that this won't fix the issue. When a dependabot job is run,...

I guess I'm not understanding what the intent is with this PR. The code makes no change to `packageSourceMapping`, it simply elevates credentials to an environment variable (and adds the...

If you are running the Ruby code directly and not through the CLI, it might be worth reviving PR #9004.

@danmoseley That property can't be resolved because the updater has no navigation path to `eng/Versions.props` (i.e., there are no direct `` elements with that.) I'm familiar with the Arcade SDK...

@danmoseley We do support `Directory.Build.props/.targets`, but the problem is [this line](https://github.com/dotnet/aspire/blob/c6545a2b60213d3095865b9dda60553aaef63aed/Directory.Build.props#L3); we don't navigate through SDK includes and crossing that boundary is what's necessary to know to eventually pull in...

I've spent the morning digging into this and I have 2 things to report: 1. Turns out we don't have property expansion hooked up for `Directory.Packages.props`, so even if we...

@austindrenski I filed #9151 to track handling property expansion inside `Directory.Packages.props`, if that's what you're referring to. If there are other issues we can certainly link them here, but "make...