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

solved it - moved to the action - `pulumi/setup-pulumi@v2` instead

<@U03EDKQ3UTY> `pulumi/setup-pulumi@v2` is also very old and no longer maintained. Please upgrade your workflow to *only* use `pulumi/actions@v3`. The setup/install part is no longer needed.
Here is a workflow using it as an example:
<https://github.com/pulumiverse/infra/blob/main/.github/workflows/push.yml>

<@UK4HNFLCB> Thanks - but I am using pulumi automation in my workflow - I am doing the set up and then `go run main.go` that eventually does a pulumi up - so I need pulumi to be installed on my machine
How can I achieve this using a newer action than `setup-pulumi@v2` ?

We have this lined up to get into `pulumi/actions`
<https://github.com/pulumi/actions/pull/834>
`setup-pulumi` will not be updated anymore.

This is in and released now: <https://github.com/pulumi/actions/releases/tag/v4.1.0>
The `command` property became optional and it mentions this:
&gt; If unspecified, the action will stop after installing Pulumi.
<@U03EDKQ3UTY> Can you give it a try?

<@UK4HNFLCB> Hey, thank you so much for the update I will try that now