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

Something super weird

When I update the pulumi-kubernetes plugin to version 4.1.0 (by advancing go.mod/go.sum and imports within the code):
1. On my Mac - it installed the 4.1.0 plugin and also the preview edited the version of the provider in the Pulumi state to 4.1.0
2. On GitHub CI - it installed the plugin specified in the state (even though the code uses `v4` objects! And ran the old provider, also didn’t update the state
I had to manually go to the GitHub state of 6 stacks and update the provider version within the state manually! Crazy
For some reason GitHub CI prefer’s the state objects but my Mac doesn’t

Same Pulumi version (v3.78.1), GitHub CI used pulumi/actions@v3