No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Hi <@U04M2C5EK97>, the relevant csproj for Automation has moved here: <https://github.com/pulumi/pulumi-dotnet/blob/main/sdk/Pulumi.Automation/Pulumi.Automation.csproj>

It seems that it does have the change, though.

Looks like pulumi core has a dependency on AspNetCore. Maybe <@U02J3T6A8LB> or <@U034YU32FHA> can help out here?

Assuming this is only with paket, because pretty sure <@U034YU32FHA> would of hit it for normal F# uses.

It does seem Paket-only, according my quick test with `pulumi preview` in `aws-fsharp` with and without Paket

I guess I should point out many (admittedly not all) F#ers use Paket... since Nuget <https://devblogs.microsoft.com/nuget/introducing-central-package-management/|until recenty> left a lot to be desired wrt transitive pinning

Workaround: `Pulumi &lt; 3.52` doesn't have the issue because `Grpc.AspNetCore` was added to `Pulumi` only <https://github.com/pulumi/pulumi-dotnet/commit/c0bf975dc3605689b1d25d807206aa7359850503#diff-9ad094494480c883d2900197d65800984774c4df8ee1f84423fe7f7743c0fc99|2 weeks ago>

Oh I can see if I can fix that, probably just re-iterating the change from <https://github.com/pulumi/pulumi/pull/6793> again

<https://github.com/pulumi/pulumi-dotnet/pull/91> &lt;- can probably get that merged and shipped today/tomorrow

Confirmed 3.53.0 fixed the issue. Thank you!