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

image.png

Hi Aurelie, thanks for the feedback on non-idempotent behavior of the publish action I've captured it in <https://github.com/pulumi/ci-mgmt/issues/565> so it gets through my team's triage and we can find out what's our current recommended best-practice here is.

&gt;  Second question: have you a release.yaml gh action optimized in order to not publish existing package (npm, pypi, nuget...)

There's been some work in that direction <https://github.com/pulumi/pulumi-package-publisher> but I'll need to double check on what remains before it's  GA and recommended for use.

It seems that the trouble is related to the version:
<https://github.com/JS-DevTools/npm-publish/issues/139#issuecomment-1715654429|https://github.com/JS-DevTools/npm-publish/issues/139#issuecomment-1715654429>

So maybe it can be useful to anyone to fix this problem.

Moreover a page in the official documentation with all the possible known issues, with a latest version of the Gh actions and all the useful information we can have could be very useful.

Very good point thank you for the suggestion!