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

I believe you need to generate a Personal Access Token with package read scope, and configure `.npmrc` and your `package.json`.

<https://blog.bitsrc.io/install-npm-private-packages-in-ci-cd-with-github-actions-746db95017cc>

We won't publish to npm, but install via git ssh links. Thanks though :heart:

GitHub has a private package repository.  You would be publishing your package to a private repository that another one of your private repositories could read from with the proper Personal Access Token scope

<@U0160HW4PHB> have you considered this approach for your use case?

I will look into it. For now, I had the chance to open source the repo, so ended up publishing to npm as an open repo. If we need a private repo, I'd probably go with npm since alpine images don't have git installed. It just works better out-of-the-box with npm.

It's not really a hard problem, but most infra issues just take so much time to solve when you have 5 different services that all need to be integrated correctly.

I’m confused if you mean you’re going to publish your package publicly on <http://npmjs.com|npmjs.com> — github also offers a private registry that you can use with the npm client <https://docs.github.com/en/packages/using-github-packages-with-your-projects-ecosystem/configuring-npm-for-use-with-github-packages>

That looks really interesting! I'll give it a chance as soon as we need to do something private.

Just having something a bit more integrated with github actions would make it all simpler

Yeah, using the github packages feature is that.  Definitely worth looking into.