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

Or this could be a bug in the GitHubActions integration. It should probably treat a Release the same way it treats a PR and target the branch

Yes I can confirm the login in the entrypoint.sh for GitHubAction is not correct

I had to create my own Pipeline from scratch and avoid the GitHubAction support for my releases for now until this is fixed.

I created an issues about stack bug <https://github.com/pulumi/actions/issues/17>

And there is also alternative Github Action for pulumi which doesn't use docker <https://github.com/prepor/github-pulumi/>

<@UPRGC0XT9> that looks significantly better...

I will try that one out and let you know...

Thanks for that man, I forked your work and created my own version of it that also supports gcloud.

&gt; created my own version of it that also supports gcloud.

but it could be done in separate action, no?

my goal was to speed up the action for my scenario, the more actions the slower it goes.

But yes, for good design I would say composability is the way to go...but I forked it so I could make my action more specific to my situation.

&gt; my goal was to speed up the action for my scenario, the more actions the slower it goes.

what speedup do you have by putting everything into a single action instead of multiple? )